Sample docs - what would you like to see? (Agile)
The VSTS process team is currently thinking about what Sample docs to include in a future version of an Agile template.
Currently we are considering this list. We'd be very interested to hear any comments on things you'd like to see - either within a doc, or other docs we should add. Or tell us what isn't so useful in an Agile setting:
Vision document and solution concept
Project start-up checklist
Personas defined
Design artefacts capturing design decisions and directions chosen
Data model & Use cases
Risk plans connected with risk work items
Threat models
Logistics / roll-out plans (Operations)
Test plans
Triage meeting notes - decisions and justifications
Iteration retrospective – meeting notes and documented learnings/changes to team working
Stakeholder matrixOne of our goals is "broad applicability", which means the docs above extend beyond what you'd expect from "pure agile". We want to support customers who are transitioning to agile or adopting agile practices into an existing framework.
Please - let us know what you think about the above sample docs. What would you like to see? What should we include, or avoid? What's useful?
Andrew
Answers
Please reply to the forum if you have any suggestions
thanks - Andrew
All Replies
Please reply to the forum if you have any suggestions
thanks - Andrew
Before you revise it, can the community argee on how MSF Agile should be applied to a reference application? What I would like to see is a complete application of the document set for Petshop4 . Observing the response of the forum community to such a case study may offer insight as to what should be revised, removed, or added to the artifact set.Hi Andrew;
I didn't see anything in this list around the "Scenario". I have found (We are expanding our MSF/Agile rollout from a small team of 10 to all of our dev teams, which is around 80 developers total) in our environment that most of the confusion seems to be around the "Scenario" and where it fits in the overall SDLC process.
Thanks.
My key documents in an agile process are:
- Vision/scope document
- Personas
- Usage Scenarios
- QoS requirements
- Solution architecture
- Project Plan
- Deployment plan and checklist
These are my top priority of what I would like to see as templates (more elaborated than the current ones...)
Please include sample docs for:
-
Scenarios
-
Persona
-
QoS
-
Development Project Plan
-
Any progress on the sample docs?
I assume all of the samples would pertain to one sample application.
I's this correct ?
After two weeks - no response.
When will the sample application be chosen ?
Any progress on the sample docs set?
Is Adventureworks LT a viable demonstration candidate?
I assume all of the samples would pertain to one sample application.
I's this correct ?
Over and above a reference implementation (with populated artificats, and perhaps samples of documents at different stages of the project) it would be excellent to get more guidance from Microsoft on overall project lifecycle management using MSF for Agile (i.e. more detail than Chapter 14 of "Team Development with Visual Studio Team Foundation Server"
14 Nov 2007 "The VSTS process team is currently thinking about what Sample docs to include in a future version of an Agile template.
Currently we are considering this list. We'd be very interested to hear any comments on things you'd like to see - either within a doc, or other docs we should add. Or tell us what isn't so useful in an Agile setting: ...."
Can anyone point me to these Sample docs ? Are they available ouside of VSTS ?
Thanks
Bob
- You can download the guidance here: http://www.microsoft.com/downloads/details.aspx?FamilyId=9F3EA426-C2B2-4264-BA0F-35A021D85234&displaylang=en
When you extract it, you will see the document templates..
You can also look at some sample deliverables here: http://www.microsoft.com/downloads/details.aspx?familyid=9D2016AD-6F8A-47F5-84FA-BEC389DB18C1&displaylang=en
Hope this helps.
These are templates , don't microsoft have contests where the whole project deliverables can be published to show some of the best practices. I have been searhcing for examples to ensure we are getting the right balance, but I can't finding any working examples , even the Teamsystem Virtual PC download is seems to be templates.
I wonder if there is enough interest in this group to construct a best practices project.
If so, then the interested members could suggest a number of Agile best practice projects.
Perhaps this has already been done ?
- hi
you can download MSF for Agile Software Development.EXE
http://www.microsoft.com/downloads/details.aspx?FamilyId=9F3EA426-C2B2-4264-BA0F-35A021D85234&displaylang=en
This download contains an update to the agile process guidance that ships with Visual Studio 2005 Team System. MSF for Agile Software Development is a scenario-driven, context-based, agile software development process that utilizes many of the ideas embodied in Team System. Version 4.1 provides new guidance for the Database Professionals to use Visual Studio Team Edition for Database Professionals ...


