Scrum and Visual Studio 2010
Click here to load reader
-
Upload
patrick-yong -
Category
Technology
-
view
5.259 -
download
0
Transcript of Scrum and Visual Studio 2010
![Page 1: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/1.jpg)
Succeeding with Agile Software Development with Scrum
Patrick Yong, MVP (SharePoint Server)http://patrickyong.net | [email protected]
![Page 2: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/2.jpg)
Agenda
−Visual Studio ALM−Scrum−Planning a project−Planning a sprint−Running a sprint−Reporting
![Page 3: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/3.jpg)
Visual Studio ALM
−Plan and Track−Design−Develop−Build−Test−Deploy
![Page 4: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/4.jpg)
Plan and Track
![Page 5: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/5.jpg)
Launching a new project
Choose process
template
Create a Team
project
Modify Area and Iteration
Tracking work Collaborate Process
GuidanceStay
Notified
![Page 6: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/6.jpg)
DEMOCreating a new Team Project
![Page 7: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/7.jpg)
Agenda
−Visual Studio ALM−Scrum−Planning a project−Planning a sprint−Running a sprint−Reporting
![Page 8: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/8.jpg)
What is Scrum?
![Page 9: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/9.jpg)
Roles
−Product owner−Scrum Master−Team role
![Page 10: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/10.jpg)
Meetings
Meeting Purpose Duration Frequency
Sprint Planning Meeting
Determine what work to do in the coming sprint.
Two hours per week in the sprint, up to four hours
Once per sprint
Daily Scrum MeetingAllow team members to commit, collaborate, and communicate risks.
Fifteen minutes Daily
Sprint Review Meeting
Show the customer and other stakeholders the work that the team accomplished in the sprint, and receive feedback.
Two hours per week in the sprint, up to four hours
Once per sprint
Retrospective Meeting
Identify and implement ideas for process improvement.
Three hours Once per sprint
![Page 11: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/11.jpg)
TFS Artifacts for Agile Development
−Work Items and Workflow−Queries−Dashboard−Excel Reports−Workbooks−Reports
![Page 12: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/12.jpg)
Why Scrum?−Iterative Development
−Lots of small “product releases” over the project’s lifetime
−As opposed to one major product release at the end
−Bugs / Problems are found early−Products are usable earlier in the process−Involves the customer during each iteration
−Iterative Development lends itself to the Scrum modus operandi−Scrum’s artifact promote customer involvement −They allow the customer to re-prioritise the order
in which “development” work is done
![Page 13: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/13.jpg)
A word of Warning
Some project managers might not like the following slides.
Viewer discretion is advised.
![Page 14: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/14.jpg)
Managing Iterative Development Using Scrum
Waterfall vs. Iterative Development
requirement gathering
analysis & design
development
testing
deployment
time
cost of
change
Customer happy, early release?
80% of a product’s value comes from 20% of its features
![Page 15: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/15.jpg)
Why focus on Iterative Development?
−Traditional, Waterfall profit & loss cost curve
![Page 16: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/16.jpg)
Why focus on Iterative Development?
−Iterative Development, early release profit & loss cost curve
![Page 17: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/17.jpg)
Agenda
−Visual Studio ALM−Scrum−Planning a project−Planning a sprint−Running a sprint−Reporting
![Page 18: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/18.jpg)
Planning the Project“As a new customer I
want to register online so I can use the services offered”
Stories are listed on the backlog in priority order
New stories are added to the product
backlog
The team estimates each story using story
points
5
8
3
5
8
1
Prio
rity
Product BacklogUser Stories
![Page 19: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/19.jpg)
Product BacklogUser Stories
Planning the Project
3
3
3
4
4
4
Sprint 3
The product owner re-prioritizes the backlogSprint 4
Stories are planned for completion in upcoming sprints
Prio
rity
![Page 20: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/20.jpg)
Planning Product Backlog
![Page 21: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/21.jpg)
What makes a good user story?
−INVEST −Independent−Negotiable−Valuable−Estimable−Small−Testable
−http://www.userstories.com/book
![Page 22: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/22.jpg)
Start writing user story
−Does your user stories answer the following?−Who the user is?−What the user need to do?−Why the user need to do that?
−“As a <user>, I need to <action> in order to <reason>”.
![Page 23: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/23.jpg)
Before you rank user stories
−Small enough to be implemented in the sprint
−Just detailed enough to describe and estimate the work that is required to implement the story
−Acceptance criteria defined
![Page 24: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/24.jpg)
Epic and Theme
−Epic −Very large user stories that represent
a significant amount of work−Theme
−User stories that are fairly large, generally larger than you would implement in a sprint
−It must be broken down into smaller user stories.
![Page 25: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/25.jpg)
Spikes
−Work that is not a direct implementation of a user story. −Research−Bug−Process improvements
![Page 26: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/26.jpg)
Prioritize your user stories
−First Things First: Prioritizing Requirements−http://www.processimpact.com/
articles/prioritizing.html
![Page 27: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/27.jpg)
Story Points
−Story points are a unit of measure for expressing the overall size of a user story
−Do not translate directly into a specific number of hours
−Less precise = less effort to determine−Do detailed estimation of hours of
work later
![Page 28: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/28.jpg)
Velocity
−Total story points in a sprint−A starting point that you can use to
determine how many user stories to implement in the sprint.
![Page 29: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/29.jpg)
Estimate Release Plan−Remember this:
−Each sprint, your team will complete an increment of the product that it could ship
−As such−Identify groups of user stories that, together,
provide enough business value to release−Determine in which sprints the team expects to
complete those groups of user stories−Note: Its OK to remove/ add user
stories to sprint
![Page 30: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/30.jpg)
DEMOProject planning with MS Excel
![Page 31: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/31.jpg)
Agenda
−Visual Studio ALM−Scrum−Planning a project−Planning a sprint−Running a sprint−Reporting
![Page 32: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/32.jpg)
Product BacklogUser Stories
Planning a Sprint
User Stories Tasks (hours)
Iteration Backlog
Commit!
Commit!
3
3
3
Can’t Commi
t!
The team breaks down
each story into tasks
The team thinks this story
is more work than they can commit to…
Based on estimates the team commits to each story
During the sprint planning meeting, the product owner and the team add User Stories
to the sprint
![Page 33: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/33.jpg)
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
Planning a Sprint
User Stories Tasks (hours)
3
3
3
3
Commit!
The larger story is removed from the
sprint and the team considers a smaller story on
the backlog
? Commit!
Commit!
The team can commit to this smaller story
The sprint is now planned and the team is ready to get
started!
![Page 34: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/34.jpg)
DEMO
![Page 35: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/35.jpg)
Agenda
−Visual Studio ALM−Scrum−Planning a project−Planning a sprint−Running a sprint−Reporting
![Page 36: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/36.jpg)
How do you Run a Sprint?− Track Progress
− Daily Sprint Meeting− What work has been completed− What work remains
− Deliver a “potentially shippable” increment
− Demo the value delivered− Retrospective
![Page 37: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/37.jpg)
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
Running a Sprint
The team starts work on the
tasks…
![Page 38: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/38.jpg)
Running a Sprint
2/1 2/4 2/72/10
2/132/16
2/192/22
2/252/28
020406080
100Remaining CompletedCompleted work
is reported daily
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
![Page 39: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/39.jpg)
Running a Sprint
2/1 2/4 2/72/10
2/132/16
2/192/22
2/252/28
020406080
100Remaining Completed
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
![Page 40: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/40.jpg)
2/1 2/4 2/72/10
2/132/16
2/192/22
2/252/28
020406080
100Remaining Completed
Running a Sprint
Each User Story has
been implemented
All work for the sprint is “done-
done”
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
![Page 41: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/41.jpg)
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
Running a Sprint
The team holds a demo to show the value they have
delivered
And the team has developed a “potentially shippable” increment
![Page 42: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/42.jpg)
Running a Sprint
The latest increment is shipped to customers
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
![Page 43: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/43.jpg)
Running a Sprint
The team holds a retrospective…
Stories delivered in the last sprint are
closed
Stories and tasks are cleared from the
backlog – the team delivered on its
commitment
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
What worked? What didn’t work? What can the team
do to improve?
![Page 44: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/44.jpg)
Running a Sprint
New Stories are added to the
Product Backlog
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
![Page 45: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/45.jpg)
Running a Sprint
The backlog is prioritized and
ready for the team to plan the next
sprint
Product BacklogUser Stories User Stories Tasks
(hours)
Iteration Backlog
![Page 46: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/46.jpg)
Agenda
−Visual Studio ALM−Scrum−Planning a project−Planning a sprint−Running a sprint−Reporting
![Page 47: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/47.jpg)
Burndown and Burn Rate
![Page 48: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/48.jpg)
Build Quality Indicator
![Page 49: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/49.jpg)
Test Plan Progress
− Unhealthy symptoms− High no. of test failed− No. of passed test remained flat
![Page 50: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/50.jpg)
Bug Status
![Page 51: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/51.jpg)
Bug Trend
−Healthy trend−Bugs discovered early−Fewer bugs towards
the end−Bugs resolved faster than
being discovered
![Page 52: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/52.jpg)
Stories Overview Report
![Page 53: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/53.jpg)
Story Progress Report
![Page 54: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/54.jpg)
DEMO
![Page 55: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/55.jpg)
Resources
−Brian Harry−http://blogs.msdn.com/bharry−Aaron Bjork
−http://blogs.msdn.com/aaronbjork/
![Page 56: Scrum and Visual Studio 2010](https://reader038.fdocuments.in/reader038/viewer/2022102321/54c7671b4a79597f648b4576/html5/thumbnails/56.jpg)