Putting the Strategies into Action
Let us consider a scenario where we have an existing infrastructure in place for a product. After the product has been in production for two years and three releases, the product manager realizes that the project team is having problems keeping up with the customer needs due to following a phased lifecycle approach that delivers once a year. The product manager decides to implement an Agile method using Scrum for the project management practices and XP for the engineering practices. A customer advisory board (CAB) is set up that is made up of key end-users who are willing to meet weekly. Also established are two customer liaisons from within the company who join the project team to continuously interact with both the team and the CAB to ensure that customer value is always considered and reassessed.
The team decides to run with two week iterations. After two iterations, the team becomes very aware that their current infrastructure, which was fine for a more phased and hierarchical approach, does not support the Agile methodology very well.
The team agrees that changes must be made. They stop progress for an iteration and instead introduce an iteration 0 which simply focuses on infrastructure change strategy and identifying the changes. They identify several infrastructure personnel to form an infrastructure team. The project and infrastructure teams decide that iteration 0 will be 1 week and focus only on identifying infrastructure improvements.