Your SlideShare is downloading. ×
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Agile development makes elephants dance
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile development makes elephants dance

1,579

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,579
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
34
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. Agile Development
    Makes the Elephants Dance
    Ethan Huang
  • 2. 敏捷开发 – 让大象跳舞
    黄方
  • 3. Ground Rules
    Mute your cell phone
    Participate – ask and answer questions
    3
  • 4. 博克软件(杭州)有限公司
  • 5. About Perficient (NSDQ:PRFT)
    A leading information technology consulting firm serving clients throughout the United States
    Perficient GDC – the 1st Agile/CMMI 5 company in China
    1 CST, 3 CSP, 30 CSD, 90+ CSM in GDC
    5
  • 6. About me
    黄方 (Ethan Huang)http://www.linkedin.com/pub/ethan-huang/b/808/9ab
    Project Manager in Perficient GDC
    10 + years development/management experience
    Waterfall, RUP, MSF, Agile/Scrum
    Certified Scrum Master/Certified Product Owner
    Certified Scrum Developer
    Certified Scrum Professional
    PMP
    6
  • 7. Warm up
    What is your DREAMsoftware development project?
    7
  • 8. The REALITY 
    Chaos Report 2009 The Standish Group
    8
  • 9. The REALITY 
    9
  • 10. Traditional Process Lifecycle Models
    Waterfall
    Spiral
    IBM RUP (Rational Unified Process)
    10
  • 11. It works!
    11
    In some specific industries:
    Military
    Space development
    ……
  • 12. Traditional process characteristics
    12
    Sequential activities
    Complicated
    Big design upfront
    Documentation/workpiece driven
    Depends on having little changes
  • 13. It doesn’t work for all the software projects
    13
  • 14. What do you feel if you join a project like this
    14
    Lasts for 48 months
    Well defined procedures
    6 months for “Envisioning”
    Hires 50 engineers
    Releases every 6 months
    1 ton of design documents
  • 15. Challenges
    15
    that I was, am, but I wish would not be facing:
    Requirement changes everyday
    Documents are never read by the engineers
    No workpiece is perfectly done
    Risks keep increasing over time
    Bad quality
    Over budget
    The project makes team down
    People are leaving
    We work 60 hours/week
    And the client is never, ever satisfied !!
  • 16. The elephant’s death march
    16
  • 17. A real story
    17
    A fixed-fee contract – budgeted 350 men/months
    5 people spent 2 months for the requirement
    Architecture/design took 2 months
    The team developed for 5 months
    Imagine what happened 6 months later in our first demo meeting
    ……
  • 18. Retrospective
    18
    Bad quality
    Team silos
    Over budget
  • 19. Why we fail?
    19
    Against changes
    Heavy up-front design losing the agility
    Focused on procedures and workpieces, instead of people
    Lost communication/cooperation/interaction with the client
  • 20. And it’s happening everywhere on this planet…
    20
  • 21. Adaption…
    21
  • 22. Agile Manifesto - 2001
    22
    http://agilemanifesto.org
    http://agilemanifesto.org/iso/zhchs/
  • 23. Agile manifesto
    23
    Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan
    个体和互动 高于 流程和工具工作的软件 高于 详尽的文档客户合作 高于 合同谈判响应变化 高于 遵循计划
  • 24. Agile methodology adoptions
    24
    MSF (Microsoft Solution Framework) Process Model
    XP (Extreme Programming)
    Lean
    Kanban
    Scrum
  • 25. Agile development characteristics
    25
    Iteratively incremental development – time boxed
    Emergent requirement – embrace changes
    JIT (Just in-time) planning, design and documentation
    Cross-functional team
    Emphasizes face-to-face communication
    Full transparency and visibility
    Frequently inspect and adapt
    Anti management pyramid
    Simple is beautiful
  • 26. Scrum overview
    26
  • 27. Scrum Framework
    27
  • 28. Scrum on one page
    28
  • 29. Low-tech tools are preferred
    29
  • 30. A real Scrum
    30
    Sprint 0 –defined the project, focusing on the short term goal,
    establish environment, etc
  • 31. A real Scrum
    31
    Sprint 1 – started from the most valuable “User Stories”
  • 32. A real Scrum
    32
    Sprint 2 – the client provided some feedback (changes), re-order
    our “Product Backlog” and adjust the plan
  • 33. A real Scrum
    33
    Sprint 3 – “velocity” increased, need more work to fulfill our
    capacity
  • 34. A real Scrum
    34
    Sprint 4 – encountered road blocker, Sprint failed 
  • 35. A real Scrum
    35
    Sprint 5 – Team made adaption after “retrospective”
  • 36. A real Scrum
    36
    Sprint 6 – came back to normal
  • 37. A real Scrum
    37
    Sprint 8 – was coming towards to the end…
  • 38. A real Scrum
    38
    Sprint 9 – delivered all the highest value requirements
  • 39. No specific engineering practices are required
    39
    However, we do have some recommendations:
    Automated Testing
    Unit Testing
    TDD (Test Driven Development)
    TDR (Test Driven Requirement)
    CI (Continuous Integration)
    UML & Design Patterns
  • 40. Success still depends on good project management skills
    40
    RID – Risks, Issues, and Dependencies
    Cost management
    People management – coaching and mentoring
    Scope management
    Scheduling & estimation
    Quality
    Communication
  • 41. Scrum project pyramid
    41
  • 42. How Agile saves the elephants
    42
    Respect to the changes
    Short iterations and short term goal
    Inspect and adapt often
    Communication and cooperation with the client
    JIT planning, design and documentation
    Simple
  • 43. However…
    43
    Agile development is not the silver bullet,
    Great people make this world different.
  • 44. Takeaways
    44
    Agile development is not just a new way to write code
    It’s a combination of practices, process and management skills
    Agile characteristics
    Scrum framework overview
  • 45. Thank you!
    45

×