Search This Blog

Showing posts with label Retrospective. Show all posts
Showing posts with label Retrospective. Show all posts

Thursday, February 6, 2014

How To Sell Agile (pt 2 of 2)

Continuing with Raja, from ProXL Consulting, and his seven reasons for using agile:

Video 3:  Reason 1. Ambiguous Requirements




Video 4:  Reason 2.  Requirements Changes are Inevitable




Watts Humphrey's Requirements Uncertainty Principle - "For a new software system, the requirements will not be completely known until after the users have used it."

Video 5:  Reason 3.  Big Upfront Planning is not practical




Video 6:  Reason 4.  Reviewing Working Software is Better Than Reviewing Documents




Video 7:  Reason 5.  Iterative and Incremental Developoment is better than Sequential Waterfall Development




Video 8:  Reasons 6 and 7.  Delivery through small baby steps is always better than a single huge delivery at project's end; and, Frequesnt reflection by the project team.




Thursday, June 28, 2012

Lessons from "Ender's Game"

Reading Orson Scott Card's excellent book "Ender's Game" Ender's retrospective upon learning of his pending transfer:

"What have I learned so far?"  Ender listed things in his mind . . . .
. . .  The enemy's gate is down;  Use my legs as a shield in battle;  A small reserve held back until the end of the game can be decisive; and, soldiers can sometime make decisions that are smarter than the orders they've been given.

The Enemy's Gate is Down

In the context of the book - this is all about knowing your objective.  Deploy your project team based on the project's objective(s) - not dogma unrelated to your specific project environment.

Use my legs as a Shield in Battle

This one is a stretch - Pass :)

A Small Reserve Held Back Until the End of the Game can be Decisive

A small reserve schedule and or financial reserve held until the end of the project can be decisive.

Soldiers can sometimes make decisions that are smarter than the orders they've been given

This is the money line!  Don't micromanage!  Instead surround yourself with brilliant people, make sure they understand the objectives, and let them make decisions using their knowledge and perspective.

Command and Control === BAD!

Autonomy === AWESOME!

Tuesday, January 24, 2012

Retrospectives

While researching Scrum, I happened across Ilan Goldstien's "Scrum Shortcuts Without Cutting Corners" blog and his post "Sprint retrospective irrespective."

I loved the concept!  Run a retrospective as an affinity diagramming session with sticky notes, a white board, and markers.  I tried it with my development team and this is what I got:


I think this technique is a keeper (as is Ilan's blog).