Introduction To Agile And Scrum

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

more share options
Embed For WordPress.com

Without related presentations

5 comments

Comments 1 - 5 of 5 previous next Post a comment

+ Robert Dempsey 6 months ago
ashutoshmjain: I’ve taken my Intro to Agile and Scrum talk and begun recording it. You can find the first video here: http://www.youtube.com/watch?v=SjTeNBlb_5Q

More to come!
+ Ashutosh Jain 6 months ago
Hi Rob - I am doing project management from last 10 yrs for large scale SAP implementations .. when I look back , I tried using the traditional approach so many times and it never worked . users just dont know what they need to begin with.

I think ... all along I was following Agile to ensure my (and projects’) success and never had a name for it .. until few years back when I learned about AGILE at IBM .

There are still many people /clients who can’t unlearn the traditional approach and make the life just too difficult

Keep up the good work

Thanks
+ Robert Dempsey 6 months ago
Thank you both for the feedback.
+ Ashutosh Jain 6 months ago
Great work
+ guest24a348 7 months ago
very much useful one.thanks

Notes on slide 1

My name is Robert Dempsey

I’m the CEO of ADS, a web development shop in Orlando

Simple project management for agile teams

Find me on Twitter

The Old Way
Requirements -> Design -> Implement -> Verify -> Maintain
Waterfall

Pros
Find bugs early in the process
Correct requirements now, less problems later (in theory)
Emphasis on documentation - developers hate doing this
Simple and disciplined
Good for stable projects

Cons
Each step is not mutually exclusive
Developers are usually (not) clairvoyant
Documentation overhead
Rigid and inflexible
Stable project?!

Reality
Development phases overlap
Software is emergent - the farther along we go the more we know
“Done” is a moving target
Flexibility is required - business requirements and the environment changes
Collaboration is essential

Lays out the philosophy for agile development
Individuals and interactions over process and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

Agile Myths
Lack of discipline - “self-managing” = do whatever you want, when you want
Lack of visibility
“That won’t work here”

What is Agile?
Group of philosophies and practices that provides the ablility to handle changing requirements
Iterative development
A lot of collaboration between business and developer
Have self-organizing and self-managing teams
Stressing leadership over management

Utilizing these and a set of practices, a team gains the ability to continuously adapt.

Agile Methods
Extreme Programming (XP)
Test Driven Development (TDD)
Feature Driven Development (FDD)
Behavior Driven Development (BDD)
Scrum

Scrum!

A framework for developing complex products and systems
Grounded in empirical process control theory
Transparency
Inspection
Adaptation
Three inspect and adapt points
Sprint Review and Planning meetings
Daily Scrum
The Retrospective

The Scrum Team
Product Owner
ScrumMaster
The Team
Called pigs: they have their bacon on the line

Involved, but aren’t committed
Users, stakeholders (customers, vendors), managers, and business units

The driving force behind the process
Helps the team and organization adopt and use Scrum
A leader, not a manager
Roles they play: coach, teacher, and supporter

Manages and controls the product backlog
Responsible for the value of the work done
Keeps the product backlog in priority order, visible to everyone
A single person, not a committee
Must have authority, and the respect of others to succeed
Single point of contact for the team

The ones turning product backlog items into increments of potentially shippable functionality
Cross-functional: everyone that needs to be on the team to make the stories happen
Self-organized: everyone contributes
No job descriptions, no titles, no exceptions
Sink or swim as a team
Optimal team size: 7, +- 2
Team composition may change at the end of a sprint; be careful in doing so

Scrum Overview
Product backlog -> release planning -> sprint (daily scrum) ->
increment -> sprint review -> sprint retrospective

Product Backlog
Managed by the Product Owner
Evolves along with the product and the environment
Master list of all functionality desired in the product
Includes all features, functions, technologies, enhancements, and bug fixes
Requirements are typically written in user story format

User Stories
How we write our requirements
From the user perspective

User Stories

Product Backlog
Sorted in order of priority
Requirements never stop changing
Minimize work: add fine-grained detail to the highest priority items (for the next few sprints)

Release Planning
Purpose: establish a plan and goals that everyone can understand and communicate
Establishes
The goals of the release
The highest priority Product Backlog items
The major risks
Overall features and functionality that the release will contain
Probable delivery date and cost if nothing changes
Composed of Sprints that deliver increments of the product, starting with the most valuable and most risky
Once enough increments are completed, release!
Most planning is done at the beginning of a release

Sprint
Sprint: 1-4 week block of time; all sprints are the same length
Protected by the ScrumMaster - no changing once it's started
Sprint Planning Meeting
When the iteration is planned
Max 8 hours for a one-month sprint, or 5% of the total Sprint length
Two parts

Sprint Planning Meeting: Part 1 - What
4 hours
The Product Owner and Team mutually determine what functionality will go into the Sprint
Considers the Product Backlog, the latest increment, team capacity, and past performance of the team
Only the team can say what they can accomplish in the upcoming Sprint
Sprint Goal: the purpose statement of the Sprint, the "why"

Sprint Planning Meeting: Part 2 - How
4 hours
Team determines how it will deliver a "done" increment
Identification of tasks - where the details are
A single task should take no more than one day
Sprint backlog - the list of tasks
Team self-organizes to assign and do the work
Negotiation between the Team and the Product Owner happens here

Sprint Backlog
All of the tasks required to turn Product Backlog items into "done" increments
Break each user story down so that changes in progress can be understood in the Daily Scrum
Modified during the Sprint as-needed
Tasks are added and removed if unnecessary
Tasks are estimated in hours, by the Team
Only the Team can change the Sprint Backlog during a Sprint
Highly-visible and real-time

Sprint Burndown
Graph showing the amount of Sprint Backlog work remaining
Variable of interest: work remaining and date

Daily Scrum
15-minute standup
The Team is responsible for having the meeting
The ScrumMaster ensures it happens, and that it stays short
3 questions
Goals
Improve communication
Eliminate other meetings
Identify and remove impediments
Highlight and promote quick decision making
Improve everyone's knowledge

Increment
Potentially shippable software: the Product Owner may decide to put it into production
Bug free, tested, clean code
Must work with everything already in place
This is where regression testing and continuous integration servers come in

Sprint Review
4-hour meeting for a one-month Sprint, or 5% of the total length of the sprint
The Scrum Team and stakeholders collaborate on what was done
Based on the feedback and changes to the Product Backlog during the Sprint, they collaborate about what to do next
Informal meeting intended to foster collaboration
Product Owner - tells what has/hasn't been done
Team - discusses what went well, what problems they ran into, and what they did to resolve them
Team - demos what's been done, and answers questions
Product Owner - discusses the Product Backlog as it stands
Group - collaborates on what to do next

Release Burndown
Graph showing the Product Backlog estimated effort remaining across time
Product Backlog estimates are reviewed and revised
Keep in mind: the Team is responsible for all estimates

Sprint Retrospective
Held between the Sprint Review and the next Sprint Planning meeting
3 hours max
ScrumMaster encourages the Team to revise their development process to become more effective
Purpose: inspect how the last Sprint went in regards to people, relationships, processes and tools
Identify and prioritize the major items that went well, and those that didn't - discuss how they can be done better
Discuss: team composition, meeting arrangements, tools, definition of "done"
Result: actionable improvement measures

Rinse and Repeat
The process begins anew

Scrum Overview
Product backlog -> release planning -> sprint (daily scrum) ->
increment -> sprint review -> sprint retrospective

Results of Agile Adoption - Agile Survey (2/08)
642 respondents
82% increased productivity

Results of Agile Adoption - Agile Survey (2/08)
77% increased quality

Results of Agile Adoption - Agile Survey (2/08)
78% increased stakeholder satisfaction

Results of Agile Adoption - Agile Survey (2/08)
37% decreased costs

Compelling arguments for at least giving it a try

Additional Information
Scrum Lunch and Learn

Additional Information
Agile Development with Scrum

20 Favorites & 1 Group

kenpachi7 favorited this 1 week ago
Oliver Wahler, Senior Concept Developer/Information Architect favorited this 2 weeks ago
R. Mathieu Landvreugd at TenICT Midrange Management, favorited this 3 weeks ago
handekaradeniz favorited this 1 month ago
Tags agile
alvaro_chang favorited this 1 month ago
Tags agiles metodolog�as
propitiated favorited this 1 month ago
jeffmcfarland favorited this 1 month ago
Kazumasa EBATA at Company, favorited this 2 months ago
Tags scrum
sselvan favorited this 4 months ago
Tags agile and scrum
evanessen favorited this 5 months ago
Tags scrum
The Indigo Heron Group, Inc., Pricipal & Co-Founder at The Indigo Heron Group, Inc., favorited this 5 months ago
Tags scrum agile projectmanagement process
dalbaragi favorited this 6 months ago
Tags scrum
Ashutosh Jain, Sr Project Manager at IBM, favorited this 6 months ago
Tags agile
bade7 favorited this 7 months ago
Ellen Feaheny, Enterprise 2.0 implementations and integrations at Customware.net, favorited this 10 months ago