My May 2008 column describes strategies for Scaling
Scrum to meet the real-world needs of project teams.
These strategies include:
- Look at the complete SDLC, not just the construction
SDLC
- Normalize the terminology
- Have a work item backlog
- Include project initiation activities, in particular
requirements and architecture envisioning
- Prove your architecture early in the lifecycle with
working code
- Explicitly include continuous independent testing in
the construction part of the lifecycle to scale TDD
- Include an explicit release/transition phase
- Include an explicit production phase to make
operations, support, and usage explicit
- Many organizations will want to address enterprise
concerns, such as enterprise architecture, reuse,
portfolio management, infrastructure administration,
human resources, governance, and so on. The
Enterprise Unified Process (EUP) provides very good
advice for this in an agile manner, see
www.enterpriseunifiedprocess.com for an overview

The column is posted at
http://www.ddj.com/architect/207100381?cid=Ambysoft .
Hope you enjoy it.

- Scott

Scott W. Ambler
Practice Leader Agile Development, IBM Methods Group
http://www.ibm.com/rational/bios/ambler.html
Agile at Scale: http://www.ibm.com/developerworks/blogs/page/ambler


__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!

http://www.flickr.com/gift/