Agile

A play in 3 sprints

Characters

A: rockstar developer

B: developer

C: intern

===== Sprint 1 ======

A: To a certain extent

B: agile tries to narrow

A: the scope of a sprint

A: in order to ship more rapidly

B: For people that have a grander vision

B: of what they want to build

===== Curtains, ship iteration 1 =====

===== Sprint 2 ======

A: this may seem narrowing

A: To be constantly reminded of the MVP.

A: If the product you're creating is a commercial thing

B: or just something that will thrive

A: based on its adoption in the marketplace

B: feature creep can be damaging

===== Curtains, ship iteration 2 =====

===== Sprint 3 ======

A: and it's helpful to have someone to keep you focused

A: on making that next shippable version

B: That's inevitably going to piss some people off

C: who are bubbling with ideas

A: and want to implement them all.

C: As a produce manager with an active imagination

A: I've been in that situation

B: and I'm slowly recovering

Chorus: :)

===== Curtains, ship iteration 3, move on to the next project =====