Accelerate Your Adoption of Agile Best Practices
By taking advantage of the unique Best Practices Analyzer (BPA), which is integrated in TeamPulse, your team can adopt Agile best practices easily and painlessly, one step at a time. The BPA is an analytical tool which automatically evaluates and then reports the project elements that do not conform to Agile best practices, allowing you to address problems early on.
Best Practices Analyzer
Our Best Practice Analyzer (BPA) can help you put the Agile theory into practice. The tool analyzes and reports the elements in your project that do not conform to best practices. For example, you can have the tool track if all requirements/stories assigned to the current iteration have a time estimate, if they are mature enough, if there is work in progress remaining in previous iterations, etc. The BPA reports allow you to take action quickly and fix any problems early on.
TeamPulse currently ships with the following 15 rules:
- Iteration duration exceeds 30 days. Iterations should rarely exceed 30 days.
- Current iteration has stories with no tasks. Stories are requirements, not work. Stories should be decomposed into tasks that represent the work required to implement the requirement.
- Current iteration has stories with no estimates. All stories assigned to the current iteration should have an estimate.
- Current iteration has stories with no personas. To help frame how users will use the software, it is a good practice to associate stories with personas.
- Current iteration stories have low or undetermined certainty. Stories that are about to be development should not have a low certainty attribute.
- Current iteration stories have low or undetermined maturity. Stories that are about to be developed should not have a low maturity attribute.
- Current iteration has stories with no acceptance criteria. Stories should have acceptance criteria (test cases) to help define when they are complete and to aid in the test definition.
- Current iteration tasks have no estimates. All tasks should have an estimate.
- Current iteration tasks have the same best, probable and worse case estimates. Rarely is it ever acceptable to have the same estimate in all three categories for one task.
- Current iteration has bugs not assigned to an area. Assigning bugs to an area helps with identification of problematic areas.
- Current iteration has problems with no estimates. The problems assigned to this iteration should have estimates in hours.
- Triaged bugs are not assigned to an area. Bugs that are triaged should be assigned to an area to help with identification of problematic areas of the project.
- Previous iterations contain work in progress. Previous iterations should only have done work, all other work should be moved forward.
- There are stories in the backlog that are marked as done. Setting status values in the backlog is not a good practice and may mean that team members have not scheduled the stories appropriately.
- There are done bugs that have no resolution. Bugs that have a done status should have a resolution entered for future reference.
- There are done stories that have ‘not done’ child stories. A story could be considered done only when all child stories are done.
With the current version it is not possible to create your own rules, but this functionality will be added in one of our next releases.
Scrum, Kanban or Scrumban, with TeamPulse you can have them all, project management couldn’t get more Agile than that. Learn more
Choose your process teamplate
Unlike other project management tools, TeamPulse does not force you into a specific process, but adapts to your team’s needs. You can use a wide range of process templates for each project like:
- Microsoft Scrum
- Microsoft Agile
- Microsoft CMMI
- Microsoft CMMI 2012
- Microsoft Scrum 2012
- Microsoft Agile 212
In addition, you can have a custom workflow that fits your own process.