Agile Use Case’s

So as you know I have worked as a Business Analyst, Quality Assurance Manager and a Scrum Master on a variety of projects. I thought I would speak today about use case creation and show you some of my examples (above) of my work. We tried to create our cases and all of our documentation on a wiki so we could have seamless collaboration between team members and the wiki provided us with an easy technology solution. We use the Use Case in the Agile Methodology to capture functional requirements. The cases capture the functional requirements of the system and or systems you will be developing, enhancing or repairing (bug fixes). You will need a representative set of use cases, covering the entire major
goals of the users and business owners. The cases are multifaceted because the architecture team uses the cases to design the components, operations/methods for the application. Test team members and also business owners will also use the cases for validation walking through diagrams for the use case steps. These are great exercises because walking through the cases will always (my experience) bring up new use cases which you could use to plan for future enhancements to the systems. I created a few guidelines I use for creating Agile Use Case’s (see below)

• Give the use case a clear name, no big soliloquy of technical jargon, all team members must understand it.
• Describe the goal that the individual use case is intended to
Accomplish in the application.
• List all the users and other systems that will
interact with the system in this use case
• List each of the steps in the use case. Don’t forget if there are multiple steps each step must be initiated in order, in accordance with
there sequence number.
• Specify all non-functional requirements related to each use
case.
• Add any issues and other notes to the case.

Popular posts from this blog

Burn Down vs. Gantt Chart

Agile/Scrum- Communication Plans

Cost Control Agile/Traditional