• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
STC Toronto Agile Intro - How can this possibly work?
 

STC Toronto Agile Intro - How can this possibly work?

on

  • 3,166 views

This is an invited talk I gave at STC Management Day in Toronto (Feb 2010). After intro, show role of docs in iterations - sometimes trailing. ...

This is an invited talk I gave at STC Management Day in Toronto (Feb 2010). After intro, show role of docs in iterations - sometimes trailing.

Let me know if you would like a copy of this presentation for your own use

Statistics

Views

Total Views
3,166
Views on SlideShare
2,814
Embed Views
352

Actions

Likes
1
Downloads
0
Comments
0

5 Embeds 352

http://agilitrix.com 316
http://www.agilitrix.com 25
http://www.slideshare.net 7
http://www.lmodules.com 2
https://api.turnitin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial LicenseCC Attribution-NonCommercial 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

    STC Toronto Agile Intro - How can this possibly work? STC Toronto Agile Intro - How can this possibly work? Presentation Transcript

    • STC Agile IntroHow can this possibly work?
      Michael Sahota
      Feb. 2010
    • Michael - 15+ years in IT
      V.P. Research and Development
      Enterprise Architect
      Director Software Development
      Architect
      Senior J2EE Developer
      Project Manager
      Team Lead
      C++ Developer
      Java Developer
      Researcher
      M.Sc. in Computer Science
      B.A.Sc. in Engineering Science
    • Michael - 8 years working with Agile
      Agile Coach
      Lean Consultant
      Scrum Master
    • Evidence that Agile Works
    • Impact of agile on productivity 88% 
      Dr Dobbs Journal, 2008 Survey. Data, summary, and slides downloadable from www.ambysoft.com/surveys/
      Copyright 2008 Scott W. Ambler www.ambysoft.com/surveys/
    • Impact of agile on quality of systems deployed  77% 
      Copyright 2008 Scott W. Ambler www.ambysoft.com/surveys/
    • Impact of agile on business stakeholder satisfaction  78% 
      Copyright 2008 Scott W. Ambler www.ambysoft.com/surveys/
    • Survey of “good time” or “best time” working at Salesforce.com
      Before Agile - 40%
      92% would
      recommend
      Agile to others
      With Agile - 86%
    • DoD prefers an Agile approach
      • After years of learning, identified evolutionary delivery (Agile) as the preferred approach over Waterfall
      • Made official policy in DoD 5000.2 (year 2000)
      Largest
      Procurer of
      Software
    • Many companies
      • Microsoft
      • Yahoo
      • Google
      • Electronic Arts
      • High Moon Studios
      • Lockheed Martin
      • Philips
      • Siemens
      • Nokia
      • Capital One
      • BBC
      • Intuit
      • Intuit
      • Nielsen Media
      • First American Real Estate
      • BMC Software
      • Ipswitch
      • John Deere
      • Lexis Nexis
      • Sabre
      • Salesforce.com
      • Time Warner
      • Turner Broadcasting
      • Oce
      CC Mountain Goat Software LLC
    • Many types of projects
      • Commercial software
      • In-house development
      • Contract development
      • Fixed-price projects
      • Financial applications
      • ISO 9001-certified applications
      • Embedded systems
      • 24x7 systems with 99.999% uptime requirements
      • the Joint Strike Fighter
      • Video game development
      • FDA-approved, life-critical systems
      • Satellite-control software
      • Websites
      • Handheld software
      • Mobile phones
      • Network switching applications
      • ISV applications
      • Some of the largest applications in use
      CC Mountain Goat Software LLC
    • Agile Values and Principles
    • TODO - Gerry
      CC Gerry Kirk
    • The Agile Manifesto sets out values
      Individuals and interactions
      over processes and tools
      Working software
      over comprehensive documentation
      Customer collaboration
      over contract negotiation
      Responding to change
      over following a plan
      Craftsmanship*
      over crap
      Common Sense
      Enabler
      While there is value in the items on the right,
      we value the items on the left more
      * 2008 proposal by Bob Martin
    • Osmotic Communication
      Copyright Alistair Cockburn
    • Principle: Face-to-face communication is fast and effective
      Copyright Alistair Cockburn
    • Documentation matters too!
      It is important that details get stored (paper, models, images, video, etc.) to handle:
      • Gaps in time - What did we decide last month?
      • Gaps in space - Keeping off-site people in the loop
      • Contracts & change of personnel
      • Traceability
    • Team Rooms – ~2x productivity
    • Agile: The Process
    • Agile processes come in different flavours
      RUP
      Agile
      Scrum
      (XP)Extreme
      Programming
      Lean
      IID
      Lean
      Software
      (Kanban)
      Crystal
      Clear
      Scrum, but…
    • Engineering Practices Matter
      Version Control
      Coding standards
      TDD
      Refactoring
    • Engineering Practices Matter
      Continuous Integration
      Automated Testing
      User Stories
      Shared code ownership
      Pairing
      CC Gerry Kirk
    • Where to learn more
    • Resources
      This presentation
      http://www.slideshare.net/michael.sahota
      Links to articles, presentations and videos
      http://www.agilitrix.com/agile-learning-resources/
      GTA Agile community events
      http://www.torontoagilecommunity.org/
    • What questions do you have?