Using GreenHopper to manage multiple teams in Agile

Managing single team in a project using any such tool sounds like a simple job but imagine a project with multiple teams having same/different backlog and accordingly sprint/milestone releases etc. Having a tool which provide a lot of flexibility and customization to help in managing all these requirements for different teams and management too seems like very challenging task. The question is to find the best solution which fits to everyone involved in the process. In this post we will explore such different requirements and will see how we can configure GreenHopper to meet such requirements.

Think of some general scenarios where team members and management might have some questions like,

• What if there are multiple teams in a project?
• What if all these teams have parallel releases for some major/milestone release?
• What if all teams share the common backlog?
• What if all teams should have their own backlog which is just sub set of whole project backlog?
• What if all teams work on different functionalities?
• What if all teams share the same code base repository?
• etc. etc.

The basic question we are targeting here is that how we can use Greenhopper to configure the tool for multiple teams and choose the right implementation approach which suits best to the teams.

Complex Scenario?

Simple scenario the project consist of single team and like any other jira project, which can be handled by single jira project. Think of complex situation where you have multiple teams working in the project.

Using Jira & GreenHopper for Backlog Management

In this post we will cover what Jira & GreenHopper offers in terms of backlog management. How you can use it to manage the different requirements of your Agile team? How to use the combination to integrate the work of different teams? What are the different functionality provided by the tool?

Product backlog

From previous post Choosing the Right Backlog Management Tool , the different parties involved in the development process of the product involved can be,

• Design Team,
• Development Team
• QA Team
• Management Team
• End Users feedback

You can have different teams involved in getting the job done and you need a tool which can integrate the work done by these different teams. Tool which can provide you better integration between all these teams, which can streamline the process of communication between teams and along with that which can also provide the single overview of backlog of all these teams.

The Atlassian Product Family