Agile, traditional or balanced mix

Mountain Goat
Software, LLC
Mr.SPOCK

Mountain Goat
Software, LLC
What you can
expect from me?

Mountain Goat
Software, LLC
Speaker
Mountain Goat
Software, LLC
Mountain Goat
Software, LLC
WOrkshOps

Mountain Goat
Software, LLC
Consulting

Mountain Goat
Software, LLC
Mountain Goat
Software, LLC
Give Knowledge

Mountain Goat
Software, LLC
Traditional vs Agile PM
•
•

•

Plan-driven
Emphasis on stable
scope

•
•

Most planning at start of
project

•

Mountain ...
What do we want?
Adopt Agile approach in the project

Meet the project goal effectively!

Mountain Goat
Software, LLC
Stages of learning
•
•

•
•
•

Level 1: Shu (―obey‖)
Traditional wisdom — learning fundamentals,
techniques.
―Do this, don...
Traditional Software Development

Long, Large, Linear, Late
Time to
Market

Lifecycle

Deliverables

Mountain Goat
Softwar...
The Project Managers
Conflict:
Successful
Project

Meet
Schedule
Granger – big cheese

Mountain Goat Software,
LLC

No
Cha...
The PMConflict:
Successful
Project
Meet
Schedule
Granger – big cheese

Mountain Goat Software,
LLC

No
Change!

Who’s to b...
Project noise level
Far from
Agreement

Requirements

Anarchy

Technology

Far from
Certainty

Mountain Goat Software,
LLC...
We‘re losing the relay race
―The… ‗relay race‘ approach to product
development…may conflict with the goals
of maximum spee...
Scrum in 100 words
• Scrum is an agile process that allows us to focus
on delivering the highest business value in the
sho...
Scrum origins
•
•

•
•

Jeff Sutherland

•
•

Initial scrums at Easel Corp in 1993
IDX and 500+ people doing Scrum

Ken Sc...
Scrum has been used by:
•Microsoft
•Yahoo
•Google
•Electronic Arts
•Lockheed Martin
•Philips
•Siemens
•Nokia
•IBM
•Capital...
Scrum has been used for:
•
•
•
•
•
•
•
•
•

Commercial software

In-house development
Contract development
Fixed-price pro...
Characteristics
•
•
•
•
•
•

Self-organizing teams
Product progresses in a series of
two-weeks/month ―sprints‖
Requirement...
A bit of history
Lean
Manufacturing
Principals

Mass
Production

Lean Software
Development

Iterative
Incremental
Developm...
The Agile Manifesto–a
statement of values
Individuals and
interactions

over

Process and tools

Working software

over

C...
Scrum

24 hours

Sprint
2-4 weeks

Sprint goal

Return
Cancel
Return
Coupons
Gift wrap
Gift wrap
Cancel
Product
backlog
Mo...
Putting it all together

Image available at
www.mountaingoatsoftware.com/scrum
Mountain Goat Software,
LLC
Agile Software Development

Iterate, Increment and Innovate
Time to
Market

1 to 6 months

Waterfall
test

Lifecycle

Deli...
Sprints

• Scrum projects make progress in a series
of ―sprints‖

•

Analogous to Extreme Programming iterations

• Typica...
Working in an Iteration

Define
Develop
Accept

Mountain Goat Software,
LLC

Fixed Time
(Iteration)

Fixed Resources

Plan...
Sequential vs.
overlapping development
Requirements

Design

Code

Test

Rather than doing all of
one thing at a time...
....
Incorrect Sprint Operation
DESIGN

SPRINT
Mountain Goat Software,
LLC

CODE

SPRINT

TEST

SPRINT
Mountain Goat Software,
LLC
Incorrect Sprint Operation
DESIGN

CODE

SPRINT
Mountain Goat Software,
LLC

TEST
Incorrect Sprint Operation
DESIGN

CODE

TEST

Mountain Goat Software,
LLC
Correct Sprint Operation
DESIGN CODE

TEST

SPRINT
Mountain Goat Software,
LLC
No changes during a sprint
Change

• Plan sprint durations around how long you
can commit to keeping change out of the
spr...
Scrum framework
Roles

•Product owner
•ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
...
Product owner

• Define the features of the product
• Decide on release date and content
• Be responsible for the profitab...
The ScrumMaster
•
•
•
•
•

•

Represents management to the project
Responsible for enacting Scrum values and
practices

Re...
The team

• Typically 5-9 people
• Cross-functional:
•

•

Programmers, testers, user experience
designers, etc.

Members ...
Queue theory – push vs pull
Pull

Push

FIMO
First In
Maybe Out

Mountain Goat Software,
LLC

FIFO
First In
First Out
Intensity
Intensity

Waterfall

Scrum

Time
Mountain Goat Software,
LLC
Scrum framework
Roles

•Product owner
•ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
...
Product backlog
• The requirements
• A list of all desired work on
the project
• Ideally expressed such that

This is the
...
Team
capacity
Product
backlog

Sprint planning meeting
Sprint prioritization

•
•

Business
conditions

Analyze and evalua...
Sprint planning
•
•
•

Team selects items from the product backlog
they can commit to completing
Sprint backlog is created...
The daily scrum
• Parameters
• Daily
• 15-minutes
• Stand-up

• Not for problem solving

• Whole world is invited
• Only t...
Everyone answers 3 questions
What did you do yesterday?
What will you do today?

Is anything in your way?

1
2
3

• These ...
Game schedule
00:05 Presentation on Product Backlog,
Sprint Planning, Daily Scrum
00:10 Sprint Planning (decide how
much t...
Scrum framework
Roles

•Product owner
•ScrumMaster
•Team

Ceremonies

•Sprint planning
•Sprint review
•Sprint retrospectiv...
The sprint review
• Team presents what it accomplished
during the sprint
• Typically takes the form of a demo of
new featu...
Sprint retrospective
• Periodically take a look at what is and is
not working
• Typically 15–30 minutes
• Done after every...
Start / Stop / Continue
• Whole team gathers and discusses what
they‘d like to:

Start doing
Stop doing
This is just one
o...
Game schedule cont‘d
00:20 Presentation on Sprint Review &
Sprint Retrospective
00:25 Sprint Review/Demo by each
team (sho...
Game schedule cont‘d
00:34 Day 1 in Sprint 2 (work)

00:38 Daily Scrum in Sprint 2
00:39 Day 2 in Sprint 2 (work)

00:43 S...
Additional slides

Mountain Goat Software,
LLC
A sample product backlog
Backlog item
Allow a guest to make a reservation
As a guest, I want to cancel a
reservation.
As a...
The sprint goal
• A short statement of what the work will be
focused on during the sprint
Life Sciences
Database Applicati...
Managing the sprint backlog
•
•
•

•
•
•

Individuals sign up for work of their own choosing

•

Work is never assigned

E...
A sprint backlog
Tasks
Code the user interface

Mon Tues Wed Thur Fri
8

4

8

Code the middle tier

16

12

10

4

Test t...
A sprint burndown chart

Mountain Goat Software,
LLC
Tasks

Mon Tues Wed Thur Fri

Code the user interface
Code the middle tier
Test the middle tier
Write online help

8
16
8
...
Scalability
•
•

•

Typical individual team is 7 ± 2 people

•

Scalability comes from teams of teams

Factors in scaling
...
Scaling through the
Scrum of scrums

Mountain Goat Software,
LLC
Scrum of scrums of scrums

Mountain Goat Software,
LLC
Where to go next
• http://mountaingoatsoftware.com/scrum
• http://scrumalliance.org
• http://controlchaos.com

Mountain Go...
A Scrum reading list
•

•
•
•
•
•
•
•
•

Agile and Iterative Development: A Manager’s Guide by
Craig Larman

Agile Estimat...
Copyright notice
•
•
•

You are free:
•
•

to Share―to copy, distribute and transmit the work
to Remix―to adapt the work

...
The Agile Manifesto invites
wimpy-ness
"… Individuals and interactions over processes & tools…"
(Yayy!! I don't have to fo...
Questions?

Mountain Goat Software,
LLC
Contacts
linkedin.com/in/vivanov
vladimir@ivanov.lv
+371 29160633
v.ivanovs
@vivanovs (Vladimir_ITSM)
Mountain Goat Softwa...
Upcoming SlideShare
Loading in …5
×

Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix

716 views

Published on

Vladimirs Ivanovs, IPMA GYCW2013 Dubrovnik Croatia, interactive workshop/game "Agile - traditional or balanced mix" or "Creating children's book with SCRUM".

About trainer:
Vladimirs is consultant and trainer in Project Management and IT Service Management, IPMA-B and ITIL Expert certified. Board member at IPMA Latvia, assessor, developing Young Crew group. Teaching Programme and Project Portfolio Management for masters in Project Management. Has a degree in Computer Sciences and Executive MBA from Stockholm School of Economics. Worked for large telecoms and as CIO for global retail chain. Owner of ITSM LLC, company that is solving IT and Project Management issues, providing consulting and trainings, CIOs and PMs for rent. Have been recently speaking on global TFT12 conference, regional Agile and Project Management events.

Published in: Business, Technology
2 Comments
1 Like
Statistics
Notes
No Downloads
Views
Total views
716
On SlideShare
0
From Embeds
0
Number of Embeds
22
Actions
Shares
0
Downloads
0
Comments
2
Likes
1
Embeds 0
No embeds

No notes for slide

Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mix

  1. 1. Agile, traditional or balanced mix Mountain Goat Software, LLC
  2. 2. Mr.SPOCK Mountain Goat Software, LLC
  3. 3. What you can expect from me? Mountain Goat Software, LLC
  4. 4. Speaker Mountain Goat Software, LLC
  5. 5. Mountain Goat Software, LLC
  6. 6. WOrkshOps Mountain Goat Software, LLC
  7. 7. Consulting Mountain Goat Software, LLC
  8. 8. Mountain Goat Software, LLC
  9. 9. Give Knowledge Mountain Goat Software, LLC
  10. 10. Traditional vs Agile PM • • • Plan-driven Emphasis on stable scope • • Most planning at start of project • Mountain Goat Software, LLC Change-driven Value Driven Delivery: Customer-valued prioritization. Relative prioritization, Incremental delivery. Frequent prototypes, demonstration Adaptive Planning: Iteration. Progressive elaboration. Less upfront planning. Planning throughout the project.
  11. 11. What do we want? Adopt Agile approach in the project Meet the project goal effectively! Mountain Goat Software, LLC
  12. 12. Stages of learning • • • • • Level 1: Shu (―obey‖) Traditional wisdom — learning fundamentals, techniques. ―Do this, don‘t do that‖ Level 2: Ha ("detach", "digress") Breaking with tradition — finding exceptions to traditional wisdom, reflecting on their truth, finding new ways, techniques, and proverbs Level 3: Ri – ("leave", "separate―) Transcendence — there are no techniques or proverbs, all moves are natural We begin from 1st level We can achieve next level only by practice  Mountain Goat Software, LLC
  13. 13. Traditional Software Development Long, Large, Linear, Late Time to Market Lifecycle Deliverables Mountain Goat Software, LLC 12 to 36 months Define MRD PRD Code Tech spec Test Code Test plan Deploy Funct test Doc Train
  14. 14. The Project Managers Conflict: Successful Project Meet Schedule Granger – big cheese Mountain Goat Software, LLC No Change! Best Product Change! Conflict* Edwards - Customer
  15. 15. The PMConflict: Successful Project Meet Schedule Granger – big cheese Mountain Goat Software, LLC No Change! Who’s to blame? -The customer?  -The project manger?  -The way we build software?  Best Product Change! Conflict* Edwards - Customer
  16. 16. Project noise level Far from Agreement Requirements Anarchy Technology Far from Certainty Mountain Goat Software, LLC Source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle. Simple Close to Certainty Close to Agreement Complex
  17. 17. We‘re losing the relay race ―The… ‗relay race‘ approach to product development…may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‗rugby‘ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today‘s competitive Hirotaka Takeuchi and Ikujiro Nonaka, requirements.‖ ―The New New Product Development Game‖, Harvard Business Review, January 1986. Mountain Goat Software, LLC
  18. 18. Scrum in 100 words • Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. • It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). • The business sets the priorities. Teams selforganize to determine the best way to deliver the highest priority features. • Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint. Mountain Goat Software, LLC
  19. 19. Scrum origins • • • • Jeff Sutherland • • Initial scrums at Easel Corp in 1993 IDX and 500+ people doing Scrum Ken Schwaber • • • ADM Scrum presented at OOPSLA 96 with Sutherland Author of three books on Scrum Mike Beedle • Scrum patterns in PLOPD4 Ken Schwaber and Mike Cohn • Co-founded Scrum Alliance in 2002, initially within the Agile Alliance Mountain Goat Software, LLC
  20. 20. Scrum has been used by: •Microsoft •Yahoo •Google •Electronic Arts •Lockheed Martin •Philips •Siemens •Nokia •IBM •Capital One •BBC Mountain Goat Software, LLC •Intuit •Nielsen Media •First American Real Estate •BMC Software •Ipswitch •John Deere •Lexis Nexis •Sabre •Salesforce.com •Time Warner •Turner Broadcasting •Oce
  21. 21. Scrum has been used for: • • • • • • • • • 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 Mountain Goat Software, LLC • 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
  22. 22. Characteristics • • • • • • Self-organizing teams Product progresses in a series of two-weeks/month ―sprints‖ Requirements are captured as items in a list of ―product backlog‖ No specific engineering practices prescribed Uses generative rules to create an agile environment for delivering projects One of the ―agile processes‖ Mountain Goat Software, LLC
  23. 23. A bit of history Lean Manufacturing Principals Mass Production Lean Software Development Iterative Incremental Development Agile Waterfall Practices RUP Scrum XP Toyota Production System Implementation 1900 1950 Your team?  1980 1990 •1986: The New, New Product development Game •1993: First Scrum team created by Jeff Sutherland •1995: Scrum formalized by Jeff Sutherland & Ken Schwaber •1999: First XP book •2001: Agile Manifesto •2001: First Scrum book by Ken Schwaber & Mike Beedle •2003: Scrum alliance formed, certification program started Mountain Goat Software, LLC Thanks to Henrik Kniberg 2000
  24. 24. The Agile Manifesto–a statement of values Individuals and interactions over Process and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan Source: www.agilemanifesto.org Mountain Goat Software, LLC
  25. 25. Scrum 24 hours Sprint 2-4 weeks Sprint goal Return Cancel Return Coupons Gift wrap Gift wrap Cancel Product backlog Mountain Goat Software, LLC Sprint backlog Coupons Potentially shippable product increment
  26. 26. Putting it all together Image available at www.mountaingoatsoftware.com/scrum Mountain Goat Software, LLC
  27. 27. Agile Software Development Iterate, Increment and Innovate Time to Market 1 to 6 months Waterfall test Lifecycle Deliverables Waterfall 12 to 36 months Working, tested code on short cycles Mountain Goat Software, LLC Waterfall deploy Waterfall documentation
  28. 28. Sprints • Scrum projects make progress in a series of ―sprints‖ • Analogous to Extreme Programming iterations • Typical duration is 2–4 weeks or a calendar month at most • A constant duration leads to a better rhythm • Product is designed, coded, and tested during the sprint Mountain Goat Software, LLC
  29. 29. Working in an Iteration Define Develop Accept Mountain Goat Software, LLC Fixed Time (Iteration) Fixed Resources Plan Story Card A Story Card B Story Card C Story Card D Story Card … Review Release Backlog
  30. 30. Sequential vs. overlapping development Requirements Design Code Test Rather than doing all of one thing at a time... ...Scrum teams do a little of everything all the time Source: ―The New New Product Development Game‖ by Takeuchi and Nonaka. Harvard Business Review, January 1986. Mountain Goat Software, LLC
  31. 31. Incorrect Sprint Operation DESIGN SPRINT Mountain Goat Software, LLC CODE SPRINT TEST SPRINT
  32. 32. Mountain Goat Software, LLC
  33. 33. Incorrect Sprint Operation DESIGN CODE SPRINT Mountain Goat Software, LLC TEST
  34. 34. Incorrect Sprint Operation DESIGN CODE TEST Mountain Goat Software, LLC
  35. 35. Correct Sprint Operation DESIGN CODE TEST SPRINT Mountain Goat Software, LLC
  36. 36. No changes during a sprint Change • Plan sprint durations around how long you can commit to keeping change out of the sprint Mountain Goat Software, LLC
  37. 37. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
  38. 38. Product owner • Define the features of the product • Decide on release date and content • Be responsible for the profitability of the product (ROI) • Prioritize features according to market value • Adjust features and priority every iteration, as needed • Accept or reject work results Mountain Goat Software, LLC
  39. 39. The ScrumMaster • • • • • • Represents management to the project Responsible for enacting Scrum values and practices Removes impediments Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Shield the team from external interferences Mountain Goat Software, LLC
  40. 40. The team • Typically 5-9 people • Cross-functional: • • Programmers, testers, user experience designers, etc. Members should be full-time • May be exceptions (e.g., database administrator) • Ideally, no titles but rarely a possibility • Teams are self-organizing • Membership should change only between sprints Mountain Goat Software, LLC
  41. 41. Queue theory – push vs pull Pull Push FIMO First In Maybe Out Mountain Goat Software, LLC FIFO First In First Out
  42. 42. Intensity Intensity Waterfall Scrum Time Mountain Goat Software, LLC
  43. 43. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
  44. 44. Product backlog • The requirements • A list of all desired work on the project • Ideally expressed such that This is the product backlog Mountain Goat Software, LLC • • each item has value to the users or customers of the product Prioritized by the product owner Reprioritized at the start of each sprint
  45. 45. Team capacity Product backlog Sprint planning meeting Sprint prioritization • • Business conditions Analyze and evaluate product backlog Select sprint goal Sprint goal Sprint planning • Current product • Technology • Mountain Goat Software, LLC Decide how to achieve sprint goal (design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours Sprint backlog
  46. 46. Sprint planning • • • Team selects items from the product backlog they can commit to completing Sprint backlog is created • • Tasks are identified and each is estimated (1-16 hours) Collaboratively, not done alone by the ScrumMaster High-level design is considered As a vacation planner, I want to see photos of the hotels. Mountain Goat Software, LLC Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)
  47. 47. The daily scrum • Parameters • Daily • 15-minutes • Stand-up • Not for problem solving • Whole world is invited • Only team members, ScrumMaster, product owner, can talk • Helps avoid other unnecessary meetings Mountain Goat Software, LLC
  48. 48. Everyone answers 3 questions What did you do yesterday? What will you do today? Is anything in your way? 1 2 3 • These are not status for the ScrumMaster • They are commitments in front of peers Mountain Goat Software, LLC
  49. 49. Game schedule 00:05 Presentation on Product Backlog, Sprint Planning, Daily Scrum 00:10 Sprint Planning (decide how much to do) 00:11 Day 1 in Sprint 1 (work) 00:15 Daily Scrum in Sprint 1 (what did you do, what will you do, obstacles) 00:16 Day 2 in Sprint 1 (work) Mountain Goat Software, LLC
  50. 50. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
  51. 51. The sprint review • Team presents what it accomplished during the sprint • Typically takes the form of a demo of new features or underlying architecture • Informal • 2-hour prep time rule • No slides • Whole team participates • Invite the world Mountain Goat Software, LLC
  52. 52. Sprint retrospective • Periodically take a look at what is and is not working • Typically 15–30 minutes • Done after every sprint • Whole team participates • ScrumMaster • Product owner • Team • Possibly customers and others Mountain Goat Software, LLC
  53. 53. Start / Stop / Continue • Whole team gathers and discusses what they‘d like to: Start doing Stop doing This is just one of many ways to do a sprint retrospective. Mountain Goat Software, LLC Continue doing
  54. 54. Game schedule cont‘d 00:20 Presentation on Sprint Review & Sprint Retrospective 00:25 Sprint Review/Demo by each team (show the work) 00:30 Sprint Retrospective (what went well, what to improve) 00:32 Sprint Planning (decide how much to do) Mountain Goat Software, LLC
  55. 55. Game schedule cont‘d 00:34 Day 1 in Sprint 2 (work) 00:38 Daily Scrum in Sprint 2 00:39 Day 2 in Sprint 2 (work) 00:43 Sprint Review/Demo by each team (show the work) 00:48 Sprint Retrospective 00:50 Wrap Up Mountain Goat Software, LLC
  56. 56. Additional slides Mountain Goat Software, LLC
  57. 57. A sample product backlog Backlog item Allow a guest to make a reservation As a guest, I want to cancel a reservation. As a guest, I want to change the dates of a reservation. As a hotel employee, I can run RevPAR reports (revenue-per-available-room) Estimate 3 5 3 8 Improve exception handling 8 ... 30 ... 50 Mountain Goat Software, LLC
  58. 58. The sprint goal • A short statement of what the work will be focused on during the sprint Life Sciences Database Application Support features necessary for population genetics studies. Make the application run on SQL Server in addition to Financial services Oracle. Support more technical indicators than company ABC with real-time, streaming data. Mountain Goat Software, LLC
  59. 59. Managing the sprint backlog • • • • • • Individuals sign up for work of their own choosing • Work is never assigned Estimated work remaining is updated daily Any team member can add, delete or change the sprint backlog Work for the sprint emerges If work is unclear, define a sprint backlog item with a larger amount of time and break it down later Update work remaining as more becomes known Mountain Goat Software, LLC
  60. 60. A sprint backlog Tasks Code the user interface Mon Tues Wed Thur Fri 8 4 8 Code the middle tier 16 12 10 4 Test the middle tier 8 16 16 11 8 8 8 8 8 8 4 Write online help Write the foo class Add error logging Mountain Goat Software, LLC 12 8
  61. 61. A sprint burndown chart Mountain Goat Software, LLC
  62. 62. Tasks Mon Tues Wed Thur Fri Code the user interface Code the middle tier Test the middle tier Write online help 8 16 8 12 4 12 16 8 10 16 7 11 50 Hours 40 30 20 10 0 Mon Mountain Goat Software, LLC Tue Wed Thu Fri 8
  63. 63. Scalability • • • Typical individual team is 7 ± 2 people • Scalability comes from teams of teams Factors in scaling • • • • Type of application Team size Team dispersion Project duration Scrum has been used on multiple 500+ person projects Mountain Goat Software, LLC
  64. 64. Scaling through the Scrum of scrums Mountain Goat Software, LLC
  65. 65. Scrum of scrums of scrums Mountain Goat Software, LLC
  66. 66. Where to go next • http://mountaingoatsoftware.com/scrum • http://scrumalliance.org • http://controlchaos.com Mountain Goat Software, LLC
  67. 67. A Scrum reading list • • • • • • • • • Agile and Iterative Development: A Manager’s Guide by Craig Larman Agile Estimating and Planning by Mike Cohn Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Software Development Ecosystems by Jim Highsmith Agile Software Development with Scrum by Ken Schwaber and Mike Beedle Scrum and The Enterprise by Ken Schwaber User Stories Applied for Agile Software Development by Mike Cohn Lots of weekly articles at www.scrumalliance.org Mountain Goat Software, LLC
  68. 68. Copyright notice • • • You are free: • • to Share―to copy, distribute and transmit the work to Remix―to adapt the work Under the following conditions • Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). Nothing in this license impairs or restricts the author‘s moral rights. • For more information see http://creativecommons.org/licenses/by/3.0/ • Credits: Mike Cohn, Mark Levison and Paul Heidema Mountain Goat Software, LLC
  69. 69. The Agile Manifesto invites wimpy-ness "… Individuals and interactions over processes & tools…" (Yayy!! I don't have to follow those stupid processes any more!) "… Working software over comprehensive documentation…" (W00t!! Dump the documentation! I LOVE this agile stuff!) "… Customer collaboration over contract negotiations…" (I'm done when I'm done and I never have to say when!) "… Responding to change over following a plan…" (No plans! No project managers! No architects! ) Mountain Goat Software, LLC Alistair Cockburn, 2010
  70. 70. Questions? Mountain Goat Software, LLC
  71. 71. Contacts linkedin.com/in/vivanov vladimir@ivanov.lv +371 29160633 v.ivanovs @vivanovs (Vladimir_ITSM) Mountain Goat Software, LLC

×