The Curious Engineer

All blogs / Software / engineering practice

Stephen Cohen's Thoughts on Agile and Project Recovery

learn.microsoft.com/en-us/archive/blogs/stephen_cohen

Software / engineering practiceEngineering management / careersMicrosoft blogsMSDN archive

’10’15’20’25
Posts
32 from 17 Nov 2006 to 27 Nov 2010
Posting
archived, read-only
Kind
personal blog
Feed
https://learn.microsoft.com/en-us/archive/blogs/stephen_cohen/feed.xml

2010 3

  1. Just when is it good enough?
  2. Who cares about your Agile development processes?
  3. 10 analogies for creating software (that aren't building construction)

2009 9

  1. Requirements are tools not weapons
  2. Fighting the Fear, Uncertainty, and Doubt
  3. It's just software ...
  4. Agile versus Formal modeling
  5. A risk-reward scale for evaluating project practices
  6. There are no right answers.
  7. Introducing Project Practice Portfolios
  8. 3 Problems that prevent delivery
  9. 5 things that make a problem worth fixing

2008 10

  1. Implement EXPILCIT Governance
  2. Project Recovery MUST beat the odds
  3. We can make the choices others can't
  4. It's not about you
  5. So you want to do project recovery?
  6. "You just don't understand ...."
  7. Don't bring a well known solution to an unknown problem
  8. Dealing with uncertainty
  9. Build Completely, Test Completely, Deploy Completely
  10. Is it project recovery or project rescue ?

2007 6

  1. During Project Recovery don't expect to educate anyone
  2. On every Recovery Project Someone Must Die
  3. What does it mean to be Agile?
  4. All is forgiven on delivery
  5. Software Project Recovery is predictable
  6. Is Recovery a dirty word?

2006 4

  1. Do we really need Status Reports?
  2. Our Team, Our Environment, and Our Customers
  3. A quick word on Process.
  4. Being Agile means It's OK to be wrong