Search code examples
agilescrumagile-processes

What is the best way to handle multiple projects when you have a single development team?

Is Agile/Scrum the answer? How does Scrum handle this?

One Product Owner, One PRoduct Backlog vs Multiple Product Owners and Product Backlogs?

How is it working for you? Please share your success failure stories?

I am trying to put a process together to manage multiple queues of work ranging from Infrastructure projects, simple feature enhancements and then big projects with a small development team of 6-7 developers.

Solution

  • I guess you can do two things:

    1. Do one release of one project, when done, do the next
    2. Split up your development team

    Or a combination of both :)

    Agile/Scrum are nice buzzwords, but don't seem very related to your question. Since they apply to the scope of a project, not to a bunch of projects.

    I have experience with the second option, up to a level where there are more projects then developers, which isn't what you want. But with decent code review sessions it does seem to work.