See Part 1
Technology: I am using Team Foundation Server 2012 Release Candidate. I believe the best tools for the scrum team are offered through Visual Studio. VS 2012 has all the features and VS2010 can't do specific tasks such as create projects however I've found using VS2010 to work well. The template used in TFS is the Visual Studio Scrum 2.0 template. Also see http://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/DEV212
Ways to work for TFS: VS has the most comprehensive feature set for working with TFS 2012. You can also use the TFS web UI, the SharePoint Foundation UI that is hooked up to TFS or excel and then import the data.
Creating PBI's: The screen shots use TFS2012 RC & VS2010. I have annotated the screenshot to help with input of PBI's. Not the priority is set from 1-1000 (default is 1000 which is the lowest priority). I like to use Mike Cohan's planning poker (uses a relative Fininacci sequence number to assign releative effort weight). The scrum team vote on estimated effort after an understanding of the user story is complete.
The scrum master has to accept the PBI and for me to do this I need 3 pieces of information namely: the user story, acceptance criteria & additional detail short clear information such as an annotated balsamiq mock-up. Obviously the product owner may negate the need for additional information but often they need to get this information from someone else in the business and I find mock-ups invaluable for clarifying to all people visual requirements.
Acceptance criteria is needed for each PBI. This would be good to have in the Sprint planning meetings. This is the format I recommend (gherkin language).
Scenario:
Given
When
Then
http://docs.behat.org/guides/1.gherkin.html
An example I have is
Scenario: Employee requests leave
Given an employyee has sufficient leave availble in the year
When the employee schedules leave (holiday)
Then the employee is informed his request is valid and his manager is informed of the request.
(Story Board)
Technology: I am using Team Foundation Server 2012 Release Candidate. I believe the best tools for the scrum team are offered through Visual Studio. VS 2012 has all the features and VS2010 can't do specific tasks such as create projects however I've found using VS2010 to work well. The template used in TFS is the Visual Studio Scrum 2.0 template. Also see http://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/DEV212
Ways to work for TFS: VS has the most comprehensive feature set for working with TFS 2012. You can also use the TFS web UI, the SharePoint Foundation UI that is hooked up to TFS or excel and then import the data.
Creating PBI's: The screen shots use TFS2012 RC & VS2010. I have annotated the screenshot to help with input of PBI's. Not the priority is set from 1-1000 (default is 1000 which is the lowest priority). I like to use Mike Cohan's planning poker (uses a relative Fininacci sequence number to assign releative effort weight). The scrum team vote on estimated effort after an understanding of the user story is complete.
The scrum master has to accept the PBI and for me to do this I need 3 pieces of information namely: the user story, acceptance criteria & additional detail short clear information such as an annotated balsamiq mock-up. Obviously the product owner may negate the need for additional information but often they need to get this information from someone else in the business and I find mock-ups invaluable for clarifying to all people visual requirements.
Acceptance criteria is needed for each PBI. This would be good to have in the Sprint planning meetings. This is the format I recommend (gherkin language).
Scenario:
Given
When
Then
http://docs.behat.org/guides/1.gherkin.html
An example I have is
Scenario: Employee requests leave
Given an employyee has sufficient leave availble in the year
When the employee schedules leave (holiday)
Then the employee is informed his request is valid and his manager is informed of the request.
Acceptance Criteria – “What is Acceptance Criteria? Put simply, it's the
criteria that defines what "Done" means for each PBI. Acceptance
Criteria is critical to the success of a Scrum team, as it becomes the
handshake between the Product Owner and the team -- it helps define what the
team is committing to.” http://www.nomad8.com/files/acceptance_criteria.php
(Story Board)
0 comments:
Post a Comment