View
4.476
Download
1
Category
Tags:
Preview:
DESCRIPTION
Work Agle with Scrum and Visual Studio 2010
Citation preview
work agile
with
scrum
and
visual studio 2010
engineering practices
testing practices
architecture practices
… practices
scrum 1
visual studio 2010 2
agile practices 3
scrum
an iterative, incremental approach to optimize
predictability and control risk.
must read
and these
must read
must studied
requirments
design
development
testing
user acceptance
release
sprint 1
sprint 2
sprint 3
sprint 4
sprint 5
release
wate
rfall
scru
m
scrum support
in visual
studio
This template allows you to organize and track the
progress and health of a small- to medium-sized
Scrum project.
team
scrummaster 1
product owner 1
the team 5± 2
the team
the Team, which does the work. The Team
consists of developers with all the skills to
turn the Product Owner’s requirements
into a potentially releasable piece of the
product by the end of the Sprint.
product owner
the Product Owner, who is responsible for
maximizing the value of the work that the
Scrum Team does.
scrum master
the ScrumMaster, who is responsible for
ensuring the process is understood and
followed.
“A chicken and a pig are together when the chicken
says, "Let's start a restaurant!"
The pig thinks it over and says, "What would we call
this restaurant?"
The chicken says, "Ham n' Eggs!"
The pig says, "No thanks, I'd be committed, but
you'd only be involved!"
pig & chicken
# Planning the project
# Product Backlog
# Release planning
meeting Estimating and prioritizing the Product Backlog
Evolving
User Needs
Owned by Product Owner
Prio by Business Value
product backlog
The Product Backlog represents everything
necessary to develop and launch a successful
product.
It is a list of all features, functions, technologies,
enhancements, and bug fixes that constitute the
changes that will be made to the product for
future releases.
in visual studio # Product Backlog
# Product Backlog
# Product Backlog
# Product Backlog
work item type product backlog item
bug
product backlog item
bug
tip: product backlog items are usually stated as
user stories. use cases are appropriate as well,
but they are better for use in developing life-
or mission critical software. www.scrumalliance.org
scenario: bugs are related to functionality being
coded during the sprint
solution: bugs are solved during in the sprint - speak
or create task -
bugs on the backlog
scenario: bugs are not related to functionality being
coded during the sprint
solution: bugs on the backlog.
solution: bugs on a separate bug backlog.
# Product Backlog
Iteration path
Iteration path
Iteration path
done
The increment must be a complete slice of the
product. It must be “done.”
Done defines what the Team means when it
commits to “doing” a Product Backlog item in a
Sprint.
grooming the backlog
The Release Burndown graph records the sum of
remaining Product Backlog estimated effort across
time.
release burndown graph
velocity is how much product backlog effort a team
can handle in one sprint
velocity graph
Looking ahead to the next version of VS Application Lifecycle Management
# Planning the sprint
# Sprint Backlog
# Sprint planning
meeting
Add PBI to sprint Decomposition Commitment
Tasks Related to PBI’s
Hours remaining
sprint backlog
The Sprint Backlog consists of the tasks the Team
performs to turn Product Backlog items into a
“done” increment.
in visual studio # Sprint Backlog
It is all of the work that the Team identifies as
necessary to meet the Sprint goal.
task
task
sprints
sprints
Sprint Backlog Burndown is a graph of the amount
of Sprint Backlog work remaining in a Sprint across
time in the Sprint.
sprint burndown graph
team capacity planning (from MSF)
sprint burndown graph in Excel from MSF
sprint planning in Excel from MSF
Looking ahead to the next version of VS Application Lifecycle Management
# Running the sprint
# Daily scrum
Track
daily scrum
The Daily Scrum is at the same time and same
place throughout the Sprints.
During the meeting, each Team member explains:
1. What he or she has accomplished since the last meeting;
2. What he or she is going to do before the next meeting; and
3. What obstacles are in his or her way.
AIT Taskboard http://www.aitgmbh.de/ Urban Turtle – Agile Planning Tools http://urbanturtle.com/
scrum boards
Looking ahead to the next version of VS Application Lifecycle Management
Looking ahead to the next version of VS Application Lifecycle Management
practices Test early and often
Build and deploy continuously
Acceptance Test Driven Development
Emergent Architectures
Refactor
Test Driven Development
Agile Database Development
Pair Programming
# Ship the sprint
# Sprint Review
# Sprint
Retrospective
Demo the value
Agile Practices – Improvement
# Product
Tasks Related to PBI’s
Hours remaining
sprint review
During the Sprint Review, the Scrum Team and
stakeholders collaborate about what was just
done. Based on that and changes to the Product
Backlog during the Sprint, they collaborate about
what are the next things that could be done.
sprint retrospective
This meeting, the ScrumMaster encourages the
Scrum Team to revise, within the Scrum process
framework and practices, its development
process to make it more effective and enjoyable
for the next Sprint.
sprints
# Sprint
Retrospective
practices
practices Test early and often
Test Driven Development
Acceptance Test Driven Development
Build and deploy continuously
Emergent Architectures
Refactor
Agile Database Development
Pair Programming
… and more
Test early and often
Test Tasks,
get test early involved
Test Driven Development
Write unit test before code
Acceptance Test Driven Development
Write acceptance tests before code
Build and deploy continuously
Deliver continuous work software
Emergent Architectures
Design vertical slices of functionality
No Big Design up Front
Refactor
RED GREEN REFACTOR
Agile Database Development
Database unit tests
Database refactoring
Pair Programming
The person typing is called the driver. The person
reviewing the code is called the observer
staat voor resultaat
Recommended