Background: a large consultant company wants to better utilize their consultants time when they're between assignments. The plan is to have an internal concept managing internal projects, which aim to deliver value to the company (sale demos, internal products, etc.) and also give the consultants the opportunity to gain new skills (for example get experience working as a Scrum Master).

Using Scrum for these projects are getting mixed results, since staff leave the projects pretty much immediatly when they get a paying assignment which makes it impossible to get a somewhat consistent velocity.

These circumstances also increase the demand on the ease of which one can enter these projects, for example readability of code, documentation of decision making etc. One risk is that this could increase the waterfall-nature of these projects, which I very much would like to avoid

So how to manage these projects? Project methods to use? Pitfalls to avoid, and how? Any help would be greatly appreciated

  • 1
    "staff leave the projects pretty much immediatly when they get a paying assignment", ummm, then pay them to stay? Commented Jan 9, 2014 at 21:42
  • Clarification: they don't leave for a different employer, they get "sold" to a new project at a customers site. Commented Jan 10, 2014 at 8:14

5 Answers 5


Scrum assumes a fixed team so like another responder said, it isn't a surprise you have found Scrum frustrating. And while saying you want to "utilize" people more pushes against the false assumptions you can 100% schedule people, however, I agree with the goals to help folks not at a client to find ways to focus on other valuable pursuits.

This sounds more like the concepts like "FedEx Days" or "80% time". Essentially, coming up with guidelines for folks but not trying to create projects with dates, deliveries or commitments. Pick up Daniel Pinks "Drive". It may also give you some ideas about how you can help motivate and guide consultants on the bench.

I've worked in consultancies and in my experience, we were always excited to work together when back at our home base. It did give us a way to make our business better and learn from each other and the challenge of leadership was to find ways to facilitate that for us while also supporting clients.

As far as more specific tools, you might try a Kanban board, but I would seriously ask why you need to measure speed (velocity or thru put). Maybe you just need a visible indicator or way to hand off or a way to see the next thing to pick up when you get back. Build the tool to suite you, don't drive it with process. Good luck

  • I agree on that Scrum is not the way to go in these types of projects, and also that measuring speed is probably not needed (I mentioned it as a problem for Scrum specifically). Commented Jan 10, 2014 at 8:07
  • Also: great answer! Will accept if nothing better comes along :) "Drive" seems like a potentially good read, will look into it. "FedEx Days" and similar approaches seem like a good idea Commented Jan 10, 2014 at 8:20

I am not sure that Scrum is the right tool for the job in this case. A similar case can be found in developing free/open source software, where contributions are intermittent and heterogeneous.

Probably a system without specific iterations, but with continuous deployment and variable velocity, like Kanban, could suit you better.


There isn't a silver bullet to fix your organization's problem that they will not invest in internal projects. The way to successfully do a project is to staff it realistically and execute with that staff. If you have folks that are simply killing time they will not be interested nor committed to their short-term-unknown duration assignment.

I would suggest that using an iterative project methodology is actually hurting you.
Why? Agile methodologies rely on a constant team with constant achievable velocity. If you have a team of 5 and in a 3-week cycle (sprint, even) you lose 2 folks, you lose control of that velocity and will either have to under-deliver or change your development cycle timeframe.

I believe your projects could be more successful if you devoted a smaller team (2 people?) to author your requirements and make some UI mockups (for example) in very small work packages, then when you get a developer on the bench, you assign him or her a small amount of work that your organization can commit to letting them finish. In our agile and non-agile projects (and some with hybrids of each) we make our definable and testable work packages as 'doable' as possible in under a week. Anything greater than 3-5 days of work is questioned in hopes of being broken apart.

  • Internal projects will keep being lower priority than external projects, since that's the way the company makes money. So it's not a problem to "fix", per se, more of the reality for these types of internal projects. Could you clarify on how you feel an iterative project methodology is hurting the projects? Commented Jan 10, 2014 at 8:16

i think best way for you is to create a backlog first , try and do vision of what exactly is that you want to achieve from this tool . Once you have backlog as mentioned above try to have 2 ppl on board for long term . These guys should understand design/requirements . Then you can keep on adding ppl around them . For an internal project no company in world will resources or money . So do demo's from time to time to update stakeholders and make use of people on pool


Scrum suggests to have a fixed team so it will be hard to track velocity for your project.

what I would suggest is to divide tasks to smallest size which can be completed within a day and then apply Kanban style development cycle. it will help to get work moving as well as you can monitor individual's contribution.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.