STC Toronto Agile Intro - How can this possibly work?

  • 2,633 views
Uploaded on

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

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,633
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. STC Agile IntroHow can this possibly work?
    Michael Sahota
    Feb. 2010
  • 2. 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
  • 3. Michael - 8 years working with Agile
    Agile Coach
    Lean Consultant
    Scrum Master
  • 4. Evidence that Agile Works
  • 5. 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/
  • 6. Impact of agile on quality of systems deployed  77% 
    Copyright 2008 Scott W. Ambler www.ambysoft.com/surveys/
  • 7. Impact of agile on business stakeholder satisfaction  78% 
    Copyright 2008 Scott W. Ambler www.ambysoft.com/surveys/
  • 8. Survey of “good time” or “best time” working at Salesforce.com
    Before Agile - 40%
    92% would
    recommend
    Agile to others
    With Agile - 86%
  • 9. DoD prefers an Agile approach
    • After years of learning, identified evolutionary delivery (Agile) as the preferred approach over Waterfall
    • 10. Made official policy in DoD 5000.2 (year 2000)
    Largest
    Procurer of
    Software
  • 11. Many companies
    CC Mountain Goat Software LLC
  • 35. Many types of projects
    • Commercial software
    • 36. In-house development
    • 37. Contract development
    • 38. Fixed-price projects
    • 39. Financial applications
    • 40. ISO 9001-certified applications
    • 41. Embedded systems
    • 42. 24x7 systems with 99.999% uptime requirements
    • 43. the Joint Strike Fighter
    • 44. Video game development
    • 45. FDA-approved, life-critical systems
    • 46. Satellite-control software
    • 47. Websites
    • 48. Handheld software
    • 49. Mobile phones
    • 50. Network switching applications
    • 51. ISV applications
    • 52. Some of the largest applications in use
    CC Mountain Goat Software LLC
  • 53. Agile Values and Principles
  • 54. TODO - Gerry
    CC Gerry Kirk
  • 55. 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
  • 56. Osmotic Communication
    Copyright Alistair Cockburn
  • 57. Principle: Face-to-face communication is fast and effective
    Copyright Alistair Cockburn
  • 58. 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?
    • 59. Gaps in space - Keeping off-site people in the loop
    • 60. Contracts & change of personnel
    • 61. Traceability
  • Team Rooms – ~2x productivity
  • 62. Agile: The Process
  • 63. Agile processes come in different flavours
    RUP
    Agile
    Scrum
    (XP)Extreme
    Programming
    Lean
    IID
    Lean
    Software
    (Kanban)
    Crystal
    Clear
    Scrum, but…
  • 64.
  • 65.
  • 66.
  • 67.
  • 68. Engineering Practices Matter
    Version Control
    Coding standards
    TDD
    Refactoring
  • 69. Engineering Practices Matter
    Continuous Integration
    Automated Testing
    User Stories
    Shared code ownership
    Pairing
    CC Gerry Kirk
  • 70. Where to learn more
  • 71. 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/
  • 72. What questions do you have?