Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Agile Principles And How To Apply In Practice

No description

Thomas Springer

on 4 May 2010

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Principles And How To Apply In Practice

Business people and developers must work
together daily
throughout the project. Build projects around
motivated individuals.
Give them the environment
and support they need,
and trust them
to get the job done.
Agile processes promote sustainable development.
The sponsors, developers,
and users should be able
to maintain a
constant pace indefinitely. Simplicity -- the art of maximizing the amount
of work not done -- is essential. The best architectures, requirements, and
designs emerge from
self-organizing teams. At regular intervals,
the team reflects
on how to become more effective, then tunes
and adjusts its behavior accordingly. Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software
frequently, from
a couple of weeks
to a couple of months,
with a preference to the
shorter timescale. The Agile Principles Our Highest Priority
Is To Satisfy The Customer
Through Early And
Continuous Delivery
Of Valuable Software create and maintain the product backlog organize the backlog into incremental releases Specify objective acceptance criteria for stories Be available to answer questions and clarify details on user stories Participate daily Verify user stories are done based on acceptance criteria Evaluate product at end of Sprint and add or remove stories from backlog as necessary Product Owner Responsibilities Time and budget (people)
are held constant,
only scope flexes Understand what users need to accomplish,
and defer feature decisions until the last
responsible moment Necessity: what minimal characteristics are necessary for this feature?
Flexibility: what would make this feature useful in more situations?
Safety: what would make this feature safer for me to use?
Comfort, Luxury, and Performance: what would make this feature more desirable to use? Build up feature quality iteration by iteration Prioritize your goals Don’t choose your
solution too early Planning is essential, plans are useless
(Eisenhower) Focus primarily on quality, and quality tends to improve and costs tend to decrease over time. Focus primarily on costs, costs tend to rise and quality falls over time. Edward Deming Result of Work Efforts
"Quality" =
Total Costs
Software teams tend to focus on “results”
with little or no regard for cost.
Management teams tend to focus on "cost"
instead of fucusing on improving the system
Scrum teams focus on improving quality, but their improvement efforts are mostly qualitative
What Does Agile Mean? Jeff Patton Jeff Patton Jeff Patton Add Nothing But Value (Eliminate Waste) The Seven Wastes of Software Development
Overproduction = Extra Features
Inventory = Requirements
Extra Processing Steps = Extra Steps
Motion = Finding Information
Defects = Defects Not Caught by Tests
Waiting = Waiting, Including Customers
Transportation = Handoffs Mary Poppendieck Mark Strange Focus on Customer value,
instead of following a plan. Pre Project
Accept Uncertainty
Pay To Keep Options Open
Pick Support Pilots
Strategic Mandate Or Kill It
F2F Prepared Workshops
Per-Magnus Skoogh, Mats Janemalm Feasibility
Test Early, Fail Fast
Long Term Product Owner Sourcing
Strong Product Owner Or Kill It Execution
Show Courage
Confront! Ask, Challenge, Discuss
Don't Touch My Sprint
Replace The Product Owner
Invest In Productivity
Require Automation, Refactoring
Recruit The Right Team
Motivated Teams Per-Magnus Skoogh, Mats Janemalm Per-Magnus Skoogh, Mats Janemalm Per-Magnus Skoogh, Mats Janemalm How Extreme Programming Addresses Waste
Develop only for today’s stories
Story cards are detailed only for the current iteration
Code directly from stories; get verbal clarification directly from customers
Have everyone in the same room; customer included
Test first; both developer tests and customer tests
Deliver in small increments
Developers work directly with customers Flow Value From Demand
(Delay Commitment) Mary Poppendieck Simple, clear purpose and principles give rise to complex, intelligent behavior. Complex rules and regulations give rise to simple, stupid behavior. Dee Hock, founder of Visa
Full transcript