When I review an approach, I find it helpful to distill it to a simple frame so I can get a bird’s-eye view.
For MSF Agile, I found the most useful frame to be the workstreams and key activities.
According to MSF, workstreams are simply groups of activities that flow logically together and are usually associated with a particular role. I couldn’t find this view in MSF Agile, so I created one:
| Workstream |
Role |
Key Activities |
| Capture Project Vision |
Business Analyst |
- Write Vision Statement
- Define Personas
- Refine Personas
|
| Create a Quality of Service Requirement |
Business Analyst |
- Brainstorm quality of Service Requirements
- Develop Lifestyle Snapshot
- Prioritize Quality of Service Requirements List
- Write Quality of Service Requirements
- Identify Security Objectives
|
| Create a Scenario |
Business Analyst |
- Brainstorm Scenarios
- Develop Lifestyle Snapshot
- Prioritize Scenario List
- Write Scenario Description
- Storyboard a Scenario
|
| Guide Project |
Project Manager |
- Review Objectives
- Assess Progress
- Evaluate Test Metric Thresholds
- Triage Bugs
- Identify Risk
|
| Plan an Iteration |
Project Manager |
- Determine Iteration Length
- Estimate Scenario
- Estimate Quality of Service Requirements
- Schedule Scenario
- Schedule Quality of Service Requirement
- Schedule bug Fixing Allotment
- Divide Scenarios into Tasks
- Divide Quality of Service Requirements into Tasks
|
| Guide an Iteration |
Project Manager |
- Monitor Iteration
- Mitigate a Risk
- Conduct Retrospectives
|
| Create a Solution Architecture |
Architect |
- Partition the System
- Determine Interfaces
- Develop Threat Model
- Develop Performance Model
- Create Architectural Prototype
- Create Infrastructure Architecture
|
| Build a Product |
Developer |
- Start a Build
- Verify a Build
- Fix a Build
- Accept Build
|
| Fix a Bug |
Developer |
- Reproduce the Bug
- Locate the Cause of a Bug
- Reassign a Bug
- Decide on a Bug Fix Strategy
- Code the Fix for a Bug
- Create or Update a Unit Test
- Perform a Unit Test
- Refactor Code
- Review Code
|
| Implement a Developer Task |
Developer |
- Cost a Development Task
- Create or Update a Unit Test
- Write Code for a Development Task
- Perform Code Analysis
- Perform a Unit Test
- Refactor Code
- Review Code
- Integrate Code Changes
|
| Close a Bug |
Tester |
- Verify a Fix
- Close the Bug
|
| Test a Quality of Service Requirement |
Tester |
- Define Test Approach
- Write Performance Tests
- Write Security Tests
- Write Stress Tests
- Write Load Tests
- Select and Run a Test Case
- Open a Bug
- Conduct Exploratory Testing
|
| Test a Scenario |
Tester |
- Define Test Approach
- Write Validation Tests
- Select and Run a Test Case
- Open a Bug
- Conduct Exploratory Testing
|
| Release a Product |
Release Manager |
- Execute a Release Plan
- Validate a Release
- Create Release Notes
- Deploy the Product
|
You Might Also Like
You Might Also Like
10 Ways to Make Agile Design More Effective
40 Hour Work Week
Agile Practices at a Glance
Don’t Let the Big Get in the Way of the Small
Don’t Push Agile, Pull It
Extreme Programming at a Glance
How To Drive Digital Transformation the Agile Way
Kanban for High-Performance Teams
MSF Agile at a Glance
Scrum at a Glance
The 4 Circles of Extreme Programming
Waterfall to Agile
What is Agile?
