Earlier this year I published the 3 Checkpoints for Your Agile Project Management Tool blog post. As a reminder, the 3 checkpoints are these:
I'm making this reference to give a clearer idea of what my today's post is about. The very first bullet — process first, tool next — deserves a closer look. What happens in the phase which goes between "process first" and "tool next'? A diagnostics check of the development process. We need to be aware of any peculiarities of the real development process to select a tool that would be capable to replicate it. So, what are the things to note about the process that one would definitely need in the tool?
First, you need to break down your development process into these 3 parts:
This high-level representation will work as a good reference framework to cover all the essential details of the process that needs to be replicated in the project management tool. I've compiled a list of questions that would help stakeholders check if a tool is capable to mirror the process. Let's go over each of those 3 major checkpoints.
1. Which work items are you using? How is work broken down in your development process? How many levels of hierarchy do you need for your work items? Just for the sake of example, the hierarchy can look as follows:
Idea (Issue) -> Epic -> Product->Project->Feature-> User Story->Task
A special attention should be paid to the levels of hierarchy, and to the ability of work items to be linked together, which brings us to the next question.
2. Which dependencies do we have between our work items? Do we need to replicate any other dependencies in the tool, apart from the hierarchical breakdown?
3. What is our definition of done for a project or for a work item? Do we need to have a certain scope completed, or is our project tied with the time elapsed? Do we need multiple final states for work items (e.g. Done and Resolved)?
1. How are people organized into teams? Do we have cross-functional teams? Functional teams? Project teams? Departments? No teams at all?
2. Is development process the same for each team? Do we sometimes need to assign several teams to an Epic or to a User Story?
3. Does anyone need to be aware of how work progresses, even if they are not assigned to this team or to this project? Customers? Executives?
1. How do we do backlog management? Where are the backlog items coming from? How do we groom the backlog?
2. Projects/Releases/Iterations: Do we have cross-project (or cross-team) releases? Parallel iterations or releases? Do we break down projects into phases (e.g. UX, prototyping, functional design, delivery)?
3. Which reports do we use? This one is very important. Be sure to check if the tool has all the reports that you need.
The reason I give this list here is that sometimes people overlook some essential components of their development process as they commit to a project management tool. I'm not claiming that each and every possible question is covered in the list above, but the 3 checkpoints framework will help to get a more complete idea of the points to note about your development process when choosing an agile project management tool.