Presentation: Implementing kanban for services team

This post share the presentation “Implementing kanban for services team” based on the different posts on Kanban shared here.

Presentation: Implementing kanban for services team

Feel free to share feedback!!!

Does Agile enforce team spirit or teamwork is enough?

One of very much overrated characteristics of Agile/Lean process is the team spirit along with teamwork. When ever we talk about the process we also talk about empowering the team, self-sufficient team, self organizing team etc. etc. The big question is does the process itself enforce the team spirit. It may demand for teamwork from each individual but how the team spirit actually works.

Teamwork

Teamwork is simply work performed by a team.

We are not yet analyzing the quality of teamwork yet, which can be communication, coordination, support etc.

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

Choosing the Right Backlog Management Tool

Sorry for staying away from the posts for this long, I have been a bit busy with the new assignment and stuff. The future plan is to share some of the learning in recent past regarding how to work out the tooling for Agile teams and lesson learned in the process. How to choose the right tool for the backlog management? What are the different tools available and what are the different factors that come into picture to take such decisions. What are the different ways to decide upon the same? We will also concentrate on some requirements which definitely change from team to team and organization to organization. It is hard to generalize these things and I will try to put some perspective to these things and see what fits best to your requirements.

The Backlog refers to the work to be done in future. Based on the process the team follows, you may need to manage different types of backlog like product backlog, sprint backlog etc. The inputs for the backlog may come from different parties involved in the process of releasing the product. The requirements may come from end users, within the team or from testing team etc. The big challenge is to stream line all this process and integrate these teams for the smooth running. To have a single tool which meets all these requirements and mapping the tools features, suitability, flexibility and maintainability with these requirements is another challenge.

There may be different parties involved in taking decision that which tool we should use and will fit the requirements

• Development team
• QA team
• Design team
• Project Management
• Organization level decision makers
• Outside world based on project requirements