Define Requirements

TeamPulse allows users to expressively define and effectively manage requirements. The product enables you to easily capture ‘user stories’ (high-level informal statements of requirements), associate them to personas (end-user profiles), create relationships between stories and much more.

enlarge screenshot

1. Write a description using the rich text formatting
2. While writing a story description, add personas and other stories on the fly by using the unique Quick Linking feature
3. Use tags
4. Set priority, estimate, status and assign to team members
5. Leave comments
6. Subscribe to get notifications when the story is modified
7. Breakdown the story into tasks
8. Add acceptance criteria
9. Attach documents, mockups or video files 

Ensure development best practices are always followed

Unlike other solutions which just passively capture data, with the built-in TeamPulse Best Practices Analyzer (BPA) you will always know when your data does not conform to Agile best practices. For example, if you schedule user stories with low maturity in the current iteration, when you run the BPA it will remind you that stories with low maturity should not be assigned to the current iteration as this could create rework later.

Learn more about the Best Practices Analyzer

Relate user stories to end-user types (personas)

TeamPulse provides you with the ability to define and manage personas – these are fictitious characters created to represent the different user types of a system. Personas help you visualize the people behind the keyboard using the software your team is creating. You can describe exactly how personas use your software by describing the interaction in a story.

enlarge screenshot

Create relationships on the fly by using the Quick Linking feature

When writing a story description in our rich text box, you can use the Quick Linking feature by pressing [Ctrl + Spacebar].This will bring up our Quick Linker which allows you to relate the current user story to other stories, personas or ideas by selecting them from a dropdown. If the story or persona that you want to use do not exist in the system, you can create them right from the Quick Linker.

enlarge screenshot

Ensure full traceability

TeamPulse will help easily create traceability relationships between ideas, feedback, feature requests, stories (requirements) and tasks, thus ensuring critical context is always saved and rework is minimized. For example, when a team member is not sure how to implement a task, he can easily trace it back to the associated user story and idea; then gaining a deeper understanding of the context of the task, he can implement it in the best way.

Decompose user stories into tasks

Many times the work needed to complete a user story can be broken down into multiple tasks.

enlarge screenshot

Specify acceptance criteria

Acceptance criteria work as an agreement between your product owner and the team to help you define when a story should be considered as ‘done.’

enlarge screenshot

Synchronize user stories and tasks with TFS 2010

TeamPulse provides two-way synchronization of User Stories and tasks with Microsoft Team Foundation Server 2010. Thanks to this integration agile software teams can benefit from TeamPulse’s improved collaboration and visualization capabilities without having to sacrifice their investments in TFS.

enlarge screenshot

Import existing stories from CVS file

TeamPulse allows users to import User Stories from a Comma Separated Value (CSV) file.

Export users stories

In addition to importing TeamPulse also allows users to export User Stories to CSV, MS Word, PDF, HTML, and ExcelML file formats.