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 |
|
Create a Quality of Service Requirement |
Business Analyst |
|
Create a Scenario | Business Analyst |
|
Guide Project | Project Manager |
|
Plan an Iteration | Project Manager |
|
Guide an Iteration | Project Manager |
|
Create a Solution Architecture | Architect |
|
Build a Product | Developer |
|
Fix a Bug | Developer |
|
Implement a Developer Task | Developer |
|
Close a Bug | Tester |
|
Test a Quality of Service Requirement | Tester |
|
Test a Scenario | Tester |
|
Release a Product | Release Manager |
|
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?
Leave a Reply