Agile in style ganesh c 12-26-12 ct buddies

Agile in Style
Course Material for CSM
by
Ganesh Chandrasekaran, BE, SCJP, CWD, PMP,CGBL, CSM
Certified ScrumMaster
December 31, 2012

How I started this?
இழபதறக எதவம் இலைல நமத ைகயிேல
ெபறவதறக உலகம் உணட தணியம் ெபொழதிேல
கலஙகி நினற நடநதெதனன ஒனறம் இலைலேய
இைடவிடொத மயறசி எனறம் ெபொயததிலைலேய
- Movie: Saatai / Lyrics: Yugabharathi

Giving a person one fish and you feed him for a day.
Teaching a person how to fish, then you feed him for a lifetime.
- Chinese Proverb

Topics to be covered
Overview of Scrum
Sprints
Product Backlog
The Team
Tracking Progress
Meetings
Release Planning
Source: Ganesh Chandrasekaran

Agile where it started
“ The... ‘relay race’ approach to product
development...may conflict with the goals of
maximum speed and flexibility. Instead a
holistic or ‘rugby’ approach - where a team
tries to go the distance as a unit, passing
the ball back and forth-may better serve
today’s competitive requirements.”

Source: Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development Game,” Harvard Business Review, January 1986.

SCRUM PROCESS
• Dr. Jeff Sutherland and Ken Schwaber
Inventors
• Scrum as a formal process at OOPSLA
'95.
• OOPSLA (Object-Oriented Programming
, Systems, Languages & Applications) is
an annual ACM research conference

Source: Wikipedia

Rugby Game
Source: Online Sources

What is Agile/SCRUM?
Scrum is an agile framework for completing
complex projects. Scrum originally was
formalized for software development
projects, but works well for any complex,
innovative scope of work. The possibilities
are endless. The Scrum framework is
deceptively simple.

Source: http://www.scrumalliance.org/learn_about_scrum

1. A product owner creates/updates product
backlog.Sprint planning, the team picks
top priority stories.
2. Team creates a sprint backlog.The team
works on a sprint, usually two to four
weeks.
3. Team meets every day to assess its
progress.The ScrumMaster keeps the
team focused on its goal.Sprint review to
showcase the product.The sprint ends
with a retrospective.Next sprint begins,
Source: http://www.scrumalliance.org/learn_about_scrum

with Step 1.


Source: http://www.mitchlacey.com/resources/scrum-framework-flow-diagram


Source: Unknown

A Sample Sprint
Mon Tue Wed Thu Fri Mon Tue Wed Thu Fri

Review
9am

Review
Daily Sync Meeting

Sprint
Sprint
10am
11am

spective
spective
Retro-
Retro-
12pm
1pm

Sprint Planning
Sprint Planning
2pm

grooming
grooming
Backlog
Backlog
3pm
4pm
5pm

Source: Mountain Goat Software

Sprint Doneness
Potentially shippable product
High Quality
Tested
Complete
Team decides the Doneness
What it does, it does very well
Show sample Doneness document

Doneness Document
Date Task

FALS 31-Dec-12 All code is checked in SVN
E
TRUE 30-Dec-12 Performed code level checks as per code review checklist
TRUE 30-Dec-12 Tested the component using multiple browsers
TRUE 30-Dec-12 All known issues updated in the Product backlog
TRUE 30-Dec-12 Test Caching of all components
FALS 31-Dec-12 All error messages/warning appearing in the log file resolved
E
FALS 31-Dec-12 All log instances are pointing to the correct logger with the appropriate log level
E
FALS 31-Dec-12 Tested components with real data
E
TRUE 30-Dec-12 Performed boundary condition checks – null values, very long strings, empty values, negative
values etc
FALS 31-Dec-12 Code should be properly commented
E
FALS 31-Dec-12 Design doc should be updated as per implementation changes
E
FALS 31-Dec-12 Change history in the code should be updated
E
TRUE 30-Dec-12 Presentation (HTML) code should be well-commented and indented as per Company standards
FALS 31-Dec-12 Designed & coded as per established standards
E
FALS 31-Dec-12 Functional testing - all applicable use cases should be documented and tested
E
TRUE 30-Dec-12 Automated testing - unit tests should be written, run and passing for all features - unit test
coverage for a component should exceed 80% code coverage - only in rare cases where unit

Architecture in Agile
Architecture is built over time
More time on Architecture initially
Gradual decrease following sprints
User valued stories less initially
Gradual increase following sprints


Sprint Commitment
The team commits to stories.
The business commits to leave priorities
alone during the sprint.
Sprint ends on same day every time.
Drop scope if needed, but don’t extend.


Story Writing
As a <user type>, I
<want/need/can/etc.> some goal, [so
that <reason>].
As a boy, I would like to grow up faster,
so that I can drive a fast car.
Stories are written by anyone.
Stories can be added anytime.


Acceptance Criteria
Adding test conditions for the story.
Can drive in all roads.
Can have music during ride.
Can go 0-60mph in 3secs.
Helps developer to code for needs.
Helps tester to create test scripts.
Test Driven Development to be followed.

Backlog Grooming
Review the stories in backlog
Re-prioritize due to changes in current
demands
Remove unwanted stories
Split epics to stories
Product backlog healthy & up to date


Product Backlog

Product Owner RAR
Defines the features of the product
Prioritizes the product backlog
Makes scope/schedule tradeoff decisions
Responsible for the profitability of the product
Adjusts priorities as more is learned
Accepts or rejects work results


ScrumMaster RAR
Helps functional and productive team
Close co-operation with cross-functional
teams
An expert in Scrum helps the team use it
A leader - self-aware, listens, flattens
hierarchy, helps colleagues improve,
coaches doesn’t control, unleashes energy
and intelligence of others.


ScrumMaster RAR
Values & practices of process & team
Removes impediments from the team
Change agent for the organization
Improves productivity as possible
If it’s legal and moral, do it


Scrum Master

The Team
Members should be full-time
Teams are self-organizing
Typically 5-9 people
Egos & attitudes are put aside
Common goal is Sprint GOAL


The Team
Rather all of one thing at a time
Does a little of everything all the time
Decide doneness as a team
Late to daily meetings have a rule
Respond emails before leaving home


The Team
Software Developers (UI/UX, Mid Tier, Back End)
Technical Architect(s)
QA Engineer(s)
Business Analyst(s)
ScrumMaster
Product Owner
Technical Writer
Project Manager


Real Life Incident

Tae Kwon Do and Scrum are both about doing the right thing in a situation rather than mastering
a list of rules

5 tenets -Tae Kwon Do
Courtesy - to help team members
Integrity - Team being whole & undivided
Perseverance - Sprint Goal
Self-Control - Team is self-organized
Indomitable Spirit - Keep the team
motivated for Sprint Success / Team
Success / Department Success

Vacation Planning Site
Show creating a backlog
Show how backlog is prioritized
Exercise the Poker game for top 10
stories
Exercise commitment with story cards
Exercise the Daily Scrum Meeting
Show the artifacts displayed in demo

Education WebSite
Site Login
Students admission
Courses with videos and text
Questionnaire end of each 30 minutes
session
Exercise compare and size the above 4
Exercise what is more critical to work first


Online Mobile App Site
Integrating Mobile Apps
Apps Ratings from users
Top 20 Apps
Exercise elaborating Epics
Exercise Acceptance Criteria needed
for stories


Sprint Planning
Who:
Team, ScrumMaster & Product Owner
Agenda:
Discuss top priority product backlog items
Team selects which items to do
Why:
Know what will be worked upon
Discuss backlog items enough to do them

Sprint Planning contd.
How full should a sprint be?
Unplanned time
Plannable time
Corporate overhead
Estimate & Analyze
Tasks estimated 1-16 hours
High-level design is considered
Time boxed to 4 hours meeting time

Sprint Planning

Commitment Driven
Pick high-priority story in backlog
Decompose it into tasks
Estimate each task
Team members ask themselves: “Can
we commit to this?”
If yes repeat with next story


Velocity Driven
Needs 4-5 sprints velocity chart
Use average or previous sprint velocity
Grab user stories equal to that velocity
Possibly stop there, but some team:
Identify tasks for selected stories
Some then estimate those tasks


Story Points
A measure of relative size of feature
Based on the total effort involved
Key is the relative size of numbers
Team does best sizing in 2-3 sprints
1,2,3,5,8,13,20,40,100
Planning Poker once a month

Daily Scrum/Sync Up
Daily sync choose a time & stick to it
15-minutes and that’s the maximum
Not for problem solving
Whole world is invited, only team talk
To reduce other meetings


Daily Scrum/Sync Up
What did you do yesterday?
What will you do today?
What, if anything, is in your way?
Each team member max 1-2 mins
Prepare 5 mins previous day - 3Qs.


Daily Scrum/Sync Standup

Scrum Task Board

Sprint Review
Team presents the product
Demo of new features or architecture
2 hours prep guideline
Whole team participates
Invite the world


Sprint Review

Sprint Retrospective
What worked very well?
What went wrong?
How can we improve?
Did we improve from last Sprint?
30-60 minutes maximum
Done after every sprint
ScrumMaster, Product Owner & Team

Sprint Retrospective

Tracking Progress
Task Boards with task current view
Burndown Charts
Release burndown chart
Sprint burndown chart
Velocity chart
Show net progress
Promote transparency
Bad News is Good News (fail early than late)

Release Planning
Sprints to complete the total backlog
Use team velocity and total story points
Hardening Sprint as needed
Release Sprint as needed
Mean Time Between Failure(MTBF) test
Stress, performance or usability testing
Compliance testing, documentation touchups


Release Sprint
Release Sprint
UAT Sprint
UAT Sprint
IT Sprint
IT Sprint
Sample Release Plan

Regular Sprint
Regular Sprint
Phase 1 Release

Regular Sprint
Regular Sprint
Hardening Sprint
Hardening Sprint
Regular Sprint
Regular Sprint
Regular Sprint
Regular Sprint
Regular Sprint
Regular Sprint
Hardening Sprint
Hardening Sprint
Regular Sprint
Regular Sprint
Regular Sprint
Regular Sprint
Regular Sprint
Regular Sprint

Succeeding with Agile
-Mike Cohn
-Mike Cohn

Succeeding with Agile
Change is not top-down or bottom-up.
The end state is unpredictable.
Scrum is pervasive.
Scrum is dramatically different.
Change is coming more quickly.
Best practices are dangerous.
Cohn, Mike (2009-10-20). Succeeding with Agile: Software Development Using Scrum (p. 5). Pearson Education (USA). Kindle Edition.


Thank You
Hope this has given an intuitive and informational session
Best Regards
Ganesh Chandrasekaran
ScrumMaster at Apple Inc.

Agile in style ganesh c 12-26-12 ct buddies

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a Agile in style ganesh c 12-26-12 ct buddies

Similar a Agile in style ganesh c 12-26-12 ct buddies (20)

Último

Último (20)

Agile in style ganesh c 12-26-12 ct buddies