Apply MSF Agile Process, A Iteration Sample for reference.
HI all.
In my job role, I am doing lots of Presaling/Education/Consultanting with VSTS and MSF.
I found lots of customer having problems to start up their first MSF Project.
When Microsoft told them, VSTS & MSF Process can make the theory to automation.
They got problems...
Not until MOC material release,
The material in MSF Process template is too fuzzy to people if they are not experience in Software process.
I saw the Graphic from Johan Traa.
But I think it’s still too abstract for our customer to Quickly Apply and understanding
Therefore, I am drawing another diagram, with snapshot and artifacts driven.(I dont know how Johan did this, I can never embed the jpg file in side this post.... too bad..)
Use some assumption in a really small project. by MSF Agile Process template.
[Assumption]
We define each iteration with cost per week.
We assume after three iteration, all the scenarios (QoS) will be captured.
The very small project probably will stay form 1.5 Month to 2 Month
[Iteration#0] -- Week # 1; Assume 30% Scenarios will be captured
Click to Image Here "http://refines.info/MSFWritting/i0.jpg"
In this iteration, after Project kickoff.
Project will move to the Envision Phase.
During this phase, that's follow the Track in MSF Agile process template.
Business Analyst will need to write down the Vision Document and Persona Document.
Upload files to Project Portal.
Since this is the first iteration.
We will transit into Build track without any activity in Plan Track.
Now is the time for Architect to do the Architecture Job describe in Build Track.
the deliverable for Team Architect might base on the Tool that the team apply.
Above diagram just describe the KEY output for Developer to go.
The Business Analyst start to write the Scenarios, GUI story board.
The Project Manager will initial the developing plan by MS Project. Put and estimate the Prioritized Scenario in Project
discuss with Developer, then split if necessary.
Finally, PM will assign the work item from Scenario to developer.
Tests will start to write the Test approach document from MSF Agile Process Template.
Developer might be busy preparing the tech skill.
At the last day of the iteration, team always has a review meeting explain in Build Track and Continuous Track.
They will open issue and discuss for any change need to update Persona or Scenario. (Log by WorkItem)
They will write down what they learn in the pass iteration and any good ideal to make it better for next Iteration.
ok... every one got the works to do. Soon one week pass. iteration#0 ending.
[Iteration#1] -- Week # 2; Assume 60% Scenarios will be captured
Click to Image "http://refines.info/MSFWritting/i1.jpg"
During this Iteration,
Developer is start to Coding.
Tester also will hand on the Testing stuff like write a Unit Test/manual test/ Web Test...etc.
If any bug/issue found, information will trace by VSTS.
Business Analyst will still busy on Scenario.
PM will monitor the progress, Prioritized issue and bugs.
One key even here is: the PM team will start to review the progress and report. at the end of iteration.
they will update the risk and triage lists. try to Prioritized the developing task for Bug and Risk.
even ask for more resource or support to re-plan.
Release Manager will start up to prepare the release plan.
detail descript in Diagram.
Team working on progress, all the artifacts will be updated and traced.
[Iteration#2] -- Week # 3; Assume 100% Scenarios will be captured
Click to Image "http://refines.info/MSFWritting/i2.jpg"
For this small project.
For this Iteration, Developer will start to Fix bug from Prioritized bug lists.
Also, Developer will start to build the system. and deploy to stage environment.
Persona team can access the system as need.
Detail descript in Diagram.
Team working on progress, all the artifacts will be updated and traced.
[Iteration#3~N] -- Week #4~N. Repeat until acceptable Release come out.
Click to Image "http://refines.info/MSFWritting/in.jpg"
Base on the review and report.
every one follow the workstream and track guild.
We verify the report to see the quality is ready to Beta/RC/RTM.
detail descript in Diagram.
Team working on progress, all the artifacts will be updated and traced.
--
A typical Project that applies the MSF Agile process might look like this.
it will of course change the iteration number and length by your team.
To share this, with the same ideal like Johan. please give me what you think for this .
Let me know if this can help you understand and quickly follow and apply the MSF Agile process?
You can get me here
polo.lee@reifnes.info
