Select Scope Manager
A commercial web-based package that provides planning capabilties to all aspects of Scrum and XP projects. Evaluation version available to download from site. I’ve worked with some Select products in the past and they’re not bad, but not very customizable.

Scarab
Java server based artifact tracking system, highly customizable. Distributed under a BSD/Apache style license.

Scrum for Team System
This is an add-in guidance package for Microsoft Team System, it fully covers Scrum and lets you get work done fast. No customizable available but it works without it. This was co-developed with Ken Schwaber so it reflects how Scrum needs to be done. Let’s users create their own views but comes with a dozen or so that are quite sufficient. Supports single team or multiple team projects and is currently being updated to version 2.0 where it’ll have more flexibility. If you have Team System in place and are struggling with the MSF for Agile package then take a look at this, you won’t be disappointed.

Although there are dozens of software solutions tools for managing agile workflow, it is best to finds the tools that are naturally adaptable in your work environment.

Just about any tool can help you and any of these tools or others can become a barrier to your success. Make the tool serve your purpose. You should not feel like you are bending to the tool’s purpose.  The tool must serve product development otherwise get rid of it.

Two common reasons you cannot get rid of a tool that is hurting you….

1. You cannot get rid of it is because someone else is mandating the tools use. Just because you paid a ton of money for a tool doesn’t mean it was a good decision and mandating a tool will not make the decision better but, it might save your career from political egg on the face. The team would dump it if they were allowed.
2. You must use a tool like the one you have to meet audit requirements. This shows up in regulated environments.

When you have the freedom to let the people who must use the tool on a regular basis make the call, don’t be surprised if this year they want tool “X”, and next year it is tool “Y”. What is more important is the ability to adapt!

There is a growing focus on the Scrum Alliance and it’s ability to help identify  training providers. The Scrum Alliance recognized education providers as they exist today are limited to the Certified Scrum Trainer (CST).

Common Training

• Certified ScrumMaster
• Certified Scrum Product Owner
• Certified Scrum Developer
• User Story Writing and Analysis
• Use Case Writing and Analysis
• Interactive Games
• User Cases
• Design Patterns
• Test Driven Development
• Refactoring
• Continuous Integration
• Object Oriented Design
• Deep Dive Scrum Master Workshops

There are more but, that is the quick list.

1. A placeholder story is a sign of sloppy planning
2. All work should be known ahead of time and planned during sprint planning
3. Yes, this allows the Product Owner to dump things into the sprint as needed.
4. Sometimes we have a history of unexpected bugs/issues of handle it now. This allows us to track how much of that is showing up and leave some slack for when it does.
5. We often have work we know we will have to do but, don’t know what it is yet.

Comment: This is a way to track how much unknown work is showing up and manage the amount by triggering a conversation when needed. One of the most common issues for scrum teams is what to do about work that we expect to have to do during a Sprint, but don’t actually know the details about yet, such as bugs we have to fix in existing systems, or expected sales support efforts. Using Place holder stories is a a method to manage these “known unknowns”.