Your SlideShare is downloading. ×
What Is Agile Management?
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

What Is Agile Management?


Published on

About being a manager in an Agile organization

About being a manager in an Agile organization

Published in: Technology, Business
  • I Got The Full File, I Just Wanna Share to You Guyszz.. It's Working You Can The Download The Full File + Instructions Here :
    Are you sure you want to  Yes  No
    Your message goes here
  • Superb presentation even just watching the slides. The sentence 60 I did not understand quite well, probably because my limited english (blush)... Would it be possible for you to explain it or make a graphical representation of it? Thank you very much!!!
    Are you sure you want to  Yes  No
    Your message goes here
  • What an excellent presentation!
    PS: Feel free to visit our 20 groups and you join us. (If not already). I'm sure some will grab your interest... You're welcome. If you wish, you can view a list of all our groups here:
    Are you sure you want to  Yes  No
    Your message goes here
  • Great as expected from Jurgen! Some very exciting slides. I would love to hear more about Slide 44 about emergent goals. Do you expect fractal goals so that the emergent goals are scale-up of existing goals?
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. What Is Agile Management? Jurgen Appelo version 3
  • 2. Jurgen Appelo writer, speaker, entrepreneur...
  • 3. Get my new book for FREE!
  • 4. Let’s begin at the beginning...
  • 5. Computer Programming Software Engineering Agile Development 1950 1960 1970 1980 1990 2000 2010
  • 6. The traditional way of looking at projects
  • 7. Split Cost (Resources) in People and Tools Split Scope in Functionality and Quality (suggestion: Scott Ambler) Add a dimension for Process (suggestion: Alistair Cockburn) Add a dimension for (Business) Value (suggestion: Jim Highsmith) Some new insights from Agile gurus
  • 8. 1. Value 2. People 3. Functionality 4. Quality 5. Tools 6. Time 7. Process And we get... the 7 dimensions of software projects
  • 9. So, what does it mean to be Agile?
  • 10. Value embracing change feedback frequent delivery value streams value mappingprioritization increments
  • 11. Example: writing a blog to find value through feedback
  • 12. People interaction collaborationsmall teams cross-functional colocation self-organization trust accountability respect
  • 13. Example: using social networks to nurture interaction
  • 14. Functionality customer involvement backlogs user stories acceptance criteria minimal marketable features user demos “inch-deep, mile-wide”
  • 15. Example: writing a book proposal as a backlog of topics
  • 16. Quality technical excellence test-driven development pair programming definition of done refactoring emergent design simplicity
  • 17. Example: using checklists as a Definition of Done
  • 18. Tools daily builds continuous integration automated testing open offices task boards burn charts version control
  • 19. Example: Using simple tools that fit the worker
  • 20. Time timeboxes iterations sprints potentially shippable products rolling wave planning sustainable pace release planning
  • 21. Example: writing in a timebox to a deadline
  • 22. Process stand-up meetings planning poker velocity spikes collective code ownership retrospectives sprint planning
  • 23. Example: Figuring out a permission requests process
  • 24. Result: A product created in a (more or less) Agile way
  • 25. So, how is the rest of the world handling Agile?
  • 26.
  • 27.
  • 28. 1. Managing Changing Priorities 2. Improved Project Visibility 3. Improved Team Morale 4. Accelerated Time to Market 5. Increased Productivity 6. Enhanced Software Quality 7. Simplified Development Process 8. Reduced Risk
  • 29.
  • 30.
  • 31. So, what should managers do to be Agile?
  • 32. Manage like a gardener
  • 33. The Management 3.0 Model
  • 34. View #1: Energize People People are the most important parts of an organization and managers must do all they can to keep people active, creative, and motivated.
  • 35. 10 Intrinsic Desires Acceptance The need for approval Curiosity The need to think Power The need for influence of will Honor Being loyal to a group Social Contact / Relatedness The need for friends Idealism / Purpose The need for purpose Status The need for social standing Independence / Autonomy Being an individual Order Or stable environments Competence / Mastery The need to feel capable
  • 36. Organize one-on-one meetings
  • 37. Organize 360 degree evaluations meetings
  • 38. View #2: Empower Teams Teams can self-organize, and this requires empowerment, authorization, and trust from management.
  • 39. 1. Tell: make decision as the manager 2. Sell: convince people about decision 3. Consult: get input from team before decision 4. Join: make decision together with team 5. Advise: influence decision made by the team 6. Confirm: ask feedback after decision by team 7. Delegate: no influence, let team work it out Use the Seven Levels of Authority
  • 40. Create an authority board
  • 41. View #3: Align Constraints Self-organization can lead to anything, and it’s therefore necessary to protect people and shared resources, and to give people a clear purpose and defined goals.
  • 42. Manage emergent and higher goals
  • 43. Do not use targets and financial/extrinsic motivation
  • 44. View #4: Develop Competence Teams cannot achieve their goals if team members aren’t capable enough, and managers must therefore contribute to the development of competence.
  • 45. 1. Self-Development 2. Coaching & Mentoring 3. Training & Certification 4. Culture & Socialization 5. Tools & Infrastructure 6. Supervision & Control 7. Management Use 7 approaches to competency
  • 46. 1. Time 2. People 3. Tools 4. Functionality 5. Quality 6. Process 7. Value 1.Individuals 2.Teams 3.Departments 4.BusinessUnits 5.Organization Prevent sub- optimization through metrics
  • 47. View #5: Grow Structure Many teams operate within the context of a complex organization, and thus it is important to consider structures that enhance communication .
  • 48. Manage the workplace as a network
  • 49. Make people’s jobs dynamic
  • 50. View #6: Improve Everything People, teams, and organizations need to improve continuously to defer failure for as long as possible.
  • 51. Apply 3 three drivers of improvement
  • 52. Apply nonlinear improvement 1, 3, 5 Kaizen Gradual improvement 2, 4 Kaikaku Radical improvement
  • 53. The Management 3.0 Model
  • 54. OK, maybe that was all a bit too much... Just remember these 2 key takeways...
  • 55. A software team is a self-organizing system Support it, don’t obstruct it
  • 56. Agile managers work the system around the team, not the people in the team
  • 57. @jurgenappelo
  • 58.
  • 59. This presentation was inspired by the works of many people, and I cannot possibly list them all. Though I did my very best to attribute all authors of texts and images, and to recognize any copyrights, if you think that anything in this presentation should be changed, added or removed, please contact me at