Upload
conscires-agile-practices
View
449
Download
1
Tags:
Embed Size (px)
Citation preview
Scrum Intro @
Orange County Product Managers
Prepared by
Bachan Anand & Yalda Shafihie [email protected]
http://agile.conscires.com
2
Agenda
IntroductionsOverview of Agile and ScrumScrum: Vision and ProductScrum: SprintScrum: ReleaseFinal ThoughtsAppendix
Overview of Agile and Scrum
4
Overview of Agile and Scrum
Agile Manifesto
Agile is a set of values: Individuals and interactions over processes
and tools Working software(Products) over
comprehensive documentation Customer collaboration over contract
negotiation Responding to change over following a plan
5
Overview of Agile and Scrum
Agile Principles
Highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software
Welcome changing requirementsDeliver working software(Product) frequentlyBusiness people and developers must work
together daily throughout the project
6
Overview of Agile and Scrum
Agile Principles
Build projects around motivated individualsMost efficient and effective method of
conveying information is face-to-face conversation
Working software(product) is the primary measure of progress
Agile processes promote sustainable development (maintain a constant pace indefinitely)
7
Overview of Agile and Scrum
Agile Principles
Continuous attention to technical excellence and good design enhances agility
Simplicity (art of maximizing amount of work not done) is essential
Best architectures, requirements, and designs emerge from self-organizing teams
At regular intervals, team reflects on how to become more effective, then tunes and adjusts
http://agilemanifesto.org/principles.html
8
Overview of Agile and Scrum
What is Scrum
Scrum is an Agile framework that supports lightweight processes that emphasize: Incremental deliveries Quality of Product Continuous improvement Discovery of people’s potential
Scrum is simple to understand, but requires discipline in order to be successful
Scrum is not a methodology
9
Overview of Agile and Scrum Foundations of Scrum
Empiricism Detailed up-front planning and defined processes are replaced by
just-in-time Inspect and Adapt cycles
Self-Organization Small teams manage their own workload and organize themselves
around clear goals and constraints
Prioritization Do the next right thing
Rhythm Allows teams to avoid daily noise and focus on delivery
Collaboration Leaders and customers work with the Team, rather than
directing them
10
Overview of Agile and Scrum Scrum Values
Transparency Everything about a project is visible to everyone
Commitment Be willing to commit to a goal
Courage Have the courage to commit, to act, to be open and to expect
respect
Focus Focus all of your efforts and skills on doing the work that you have
committed to doing
Respect Respect and trust the different people who comprise a team
Scrum: Vision and Product
12
Scrum: Vision and Product
Vision
A goal to aspire toCan be
summarized in a short statement of intent
Communicate it to the team
Scrum: Vision and Product
Role: Product Owner13
Thought Leader and VisionaryDrives the Product Vision (for example, with
Story Mapping)Prioritizes the User Stories Maintains the Product Backlog with the teamAccepts the Working Product (on behalf of
the customer)
14
Scrum: Vision and Product
User Stories
Product requirements formulated as one or more sentences in the everyday or business language of the user As a <user>, I would like <function> so that I get
<value>
Each User Story has an associated Acceptance Criteria that is used to determine if the Story is completed
15
Scrum: Vision and Product
User Stories
Independent Not overlap in concept and be able to schedule and implement them in any
order
Negotiable Not an explicit contract for features; rather, details will be co-created by
Product Owner and Team
Valuable Add business value
Estimated Just enough to help the Product Owner rank and schedule the story's
implementation
Sized Appropriately Need to be small, such as a few person-days
Testable A characteristic of good requirements
16
Scrum: Vision and Product
Product Backlog
A living list of requirements captured in the form of User Stories
Represents the WHAT of the systemPrioritization with respect to business value is
essential!Each story has estimated Story Points, which
represent relative size, and is determined by those actually doing the work
Higher priority items are decomposed and lower priority items are left as larger stories (epics)
Scrum: Sprint
18
Scrum: Sprint
Role: ScrumMaster
Servant LeaderFacilitates the ProcessSupports the TeamRemoves Organizational ImpedimentsSocializes Scrum to Management
Enable close collaboration across all roles and functions
19
Scrum: Sprint
Role: Team
Cross-Functional 5-8 MembersSelf-OrganizingFocused on meeting Commitments
20
Scrum: Sprint
Role: Relationships
Scrum: Sprint
Sprint Cycle21
22
Scrum: Sprint
Flow & Artifacts: Planning
Sprint Planning meeting held at beginning of each Sprint
Time and Resources are fixed in any given Sprint Goal is to have prioritized Sprint Backlog,
broken down into tasks, that the Team can commit to
During planning, Team commits to scope that can be completed in the Sprint, taking into account the definition of Done
Story points may be refined
Scrum: Sprint
Flow & Artifacts: Sprint Backlog23
List of stories, broken down into tasks, that is committed for any particular Sprint
Owned and managed by the Team
Any team member can add, delete or change the sprint backlog with additional tasks
24
Scrum: Sprint
Flow & Artifacts: Done
Team creates its own definition of Done in the interest of creating quality software
Definition can evolve over sprintsExample checklist (not exhaustive):
Unit tests pass (ideally automated) Customer Acceptance tests pass User docs written UI design approved by PO Integrated into existing system Regression test/s pass (ideally automated) Deployed on staging server Performance tests pass
25
Scrum: Sprint
Flow & Artifacts: Daily Standup
Meetings held in same location, same time, every day
Timeboxed at 15 minutesEncourages self-organization, rhythm, and
collaborationNot a status meetingEach Team member speaks to:
What did I accomplish in the last 24 hours What do I plan to accomplish in the next 24 hours Any impediments getting in the way of my work
26
Scrum: Sprint
Flow & Artifacts: Taskboard
Active visual indicator of flow of work
Should be visible to team members at all times
Should be kept current
Encourages self-organization, and collaboration
27
Scrum: Sprint
Flow & Artifacts: Sprint Burndown
Shows daily progress in the Sprint
X-axis is the number of days in the Sprint
Y-axis is the number of remaining stories
28
Scrum: Sprint
Flow & Artifacts: Sprint Review
Occurs at the end of each SprintInspect and Adapt the product (Empiricism)The team meets with the Product Owner (and
Stakeholders) to demonstrate the working software from the Sprint
This is a hands-on software demo (not a PowerPoint) that usually requires some prep beforehand
29
Scrum: Sprint
Flow & Artifacts: Retrospective
Occurs at the end of each SprintInspect and Adapt the process (Empiricism)Team and ScrumMaster meet to reflect on
what went well and what can be improvedTone of the meeting is that everyone did their
best and now look to how can we improveRetrospectives must conclude with team
commitments to action
Scrum: Release
31
Scrum: Release
Flow & Artifacts: Velocity
Total number of story points completed by a team in a Sprint
Can be used by the team as a reference during Sprint Planning
Used by Product Owner to plan out the releases
32
Scrum: Release
Flow & Artifacts: Release Planning
Product Owner, in conjunction with the team, formulates Release Plans by applying the team Velocity to the Product Backlog
Release Plans are revisited after every SprintTwo ways to approach
Fix scope and determine how many sprints are needed Fix time and determine how much scope can be
completed
Scrum: Release
Flow & Artifacts: Release Burndown33
Shows progress across Sprints
X-axis is the number of Sprints
Y-axis is the total number of stories
Final Thoughts
35
Scrum is a lightweight framework with a simple set of rules, built on foundations and values
Scrum enables teams to discover their true potential and deliver quality software that adds business value
Appendix
37
Appendix
Roles
Product Owner Thought Leader and Visionary, who drives the Product
Vision, maintains the Product Backlog, prioritizes the User Stories, and accepts the Working Software (on behalf of the customer)
ScrumMaster Servant Leader, who facilitates the process, supports the
Team, removes organizational impediments, and socializes Scrum to Management
Team Cross-Functional group of 5-8 Members that is self-
organizing and focused on meeting Commitments
38
Appendix
Artifacts
Product Backlog A living list of requirements captured in the form of User Stories,
prioritized according to business value
Sprint Backlog List of stories, broken down into tasks, that is committed for any
particular Sprint; owned and managed by the Team
Taskboard Active visual indicator of flow of work
Sprint Burndown Chart Shows daily progress in the Sprint
Release Burndown Chart Shows progress across Sprints
39
Appendix
Planning (Ceremonies)
Sprint Planning Held at beginning of each Sprint, with the goal to have prioritized
Sprint Backlog, broken down into tasks, that the Team can commit to
Daily Standup Meetings held in same location, same time, every day, with the goal
of ensuring that team members are in synch (not a status meeting)
Sprint Review Occurs at the end of each Sprint, with the goal of inspecting and
adapting the Product
Retrospective Occurs at the end of each Sprint, with the goal of inspecting and
adapting the process
40
Thank you !