• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Being Agile
 

Being Agile

on

  • 2,243 views

"Being Agile" presents an introduction to Scrum, an Agile software development methodology. In addition to the basics of the iterative development process and roles, this talk explores Agile concepts ...

"Being Agile" presents an introduction to Scrum, an Agile software development methodology. In addition to the basics of the iterative development process and roles, this talk explores Agile concepts related to requirements, documentation, communication, planning, and overall business strategy.

Presented to Cedar Rapids IIBA 2/10/2010

Statistics

Views

Total Views
2,243
Views on SlideShare
2,226
Embed Views
17

Actions

Likes
2
Downloads
48
Comments
0

4 Embeds 17

http://www.davidsturtz.com 7
http://davidsturtz.com 6
http://www.slideshare.net 2
http://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Being Agile Being Agile Presentation Transcript

    • being agile David Sturtz david@davidsturtz.com twitter: @sturtz
    • Hi. I’m David. Product Manager, Geonetric Information Architect / UX Designer Certified Scrum Master
    • Many denominations Agile Unified Process, Crystal, Dynamic Systems Development, Extreme Programming (XP), Feature Driven Development (FDD), Lean Software Development, Scrum, etc. I will generally be talking from a Scrum perspective.
    • Why Agile?
    • Waterfall… Requirements Design Implementation Verification Maintenance
    • …or other ‘methods’.
    • Q: Ought form to derive from the analysis of function? A: The great risk here is that the analysis may not be complete. — Charles Eames
    • Why Agile? Change is constant. Development is design. Human interactions. Collaboration. Inspect & adapt. Build quality in. Demonstrable value. Aligned with goals.
    • What is Agile? Project Management Process Leadership Philosophy Engineering Practices Business Approach Jon Strickler, Defining Agile Development
    • How will we get there? Agile is a project management process. Jon Strickler, Defining Agile Development
    • Resources Scope Quality Time
    • Resources Scope Quality Time
    • Team Backlog ‘Done’ Iteration
    • Team Backlog 2 weeks to 30 days ‘Done’ fixed goalpost Iteration
    • Scrum Stand-up 24 hours Product Backlog Sprint/Iteration 2 weeks to 30 days Sprint Potentially Backlog Shippable Increment Adapted from Mountain Goat Software
    • planning Team Backlog daily stand-up ‘Done’ review Iteration retrospective
    • The Scrum Board To Do ∂ In Progress ∂ Complete ∂ Accepted
    • The Burndown
    • Who is in charge? Agile is a leadership philosophy. Jon Strickler, Defining Agile Development
    • Team Backlog team members ‘Done’ scrum master product owner Iteration
    • 7±2 Team Backlog committed ‘Done’ co-located cross-functional Iteration self-organizing
    • Inspect and adapt “Agility might be said to be about encountering all the problems so early and so often that the e fort to fix them is less than the pain of enduring them.” — Ron Jeffries
    • When are we finished? Agile is a set of engineering best practices. Jon Strickler, Defining Agile Development
    • Team Backlog demonstrable value ‘Done’ definition of ‘done’ team owns quality Iteration
    • Slices, not layers
    • Done-done. “If we’re not shipping our software when it’s ready, it’s poor business practice. If we’re not sure whether our software is ready, it’s poor software practice.” — Ron Jeffries
    • What are your priorities? Agile is a business approach. Jon Strickler, Defining Agile Development
    • Team Backlog user stories ‘Done’ acceptance criteria prioritized Iteration
    • The User Story As a USER I want GOAL so that VALUE
    • Strategy Executive Years Team Portfolio Product Product Management Planning Release Months Iteration Development Team Daily Hours Adapted from Rich Mironov/Enthiosys Planing Time Horizons
    • Fail early, fail often. “By far the dominant reason for not releasing sooner was a reluctance to trade the dream of success for the reality of feedback.” — Kent Beck
    • Team Backlog ‘Done’ Iteration
    • What is Agile? Project Management Process Leadership Philosophy Engineering Practices Business Approach Jon Strickler, Defining Agile Development
    • What is Agile? “Simplicity does not precede complexity, but follows it.” — Alan Perlis
    • being agile David Sturtz david@davidsturtz.com twitter: @sturtz
    • Recommended Reading
    • Photo Credits Sekitei Garden by mrhayata Handful of Frogs at Coba by deanj http://www.flickr.com/photos/mrhayata/ http://www.flickr.com/photos/deanj/67607256/ 100841819/ Zen Gravel by Seldom Scene Photography 1/2 Kishu Roll by Geoff Peters 604 http://www.flickr.com/photos/old_dog_photo/ http://www.flickr.com/photos/gpeters/ 4227016718/ 3453508591/ Busy sprint by drewgstephens Zen garden - Ginkakuji by Stéfan http://www.flickr.com/photos/dinomite/ http://www.flickr.com/photos/st3f4n/ 3219513356/ 2750491245/ eames shell chair by back garage Cascade by vandelizer http://www.flickr.com/photos/ http://www.flickr.com/photos/jeremy_vandel/ back_garage/3650087649/ 208714007/ WikiData User Stories by psd http://www.flickr.com/photos/psd/3731275681/