A common failure mode for organisations attempting to adopt an Agile style of software development occurs when an attempt is made to “Scale Agile”. Suddenly, the organisation finds that there are scheduling problems between teams. Delivery team members suddenly find that they are required to serve on several teams at once. Dependencies surface, and teams find it difficult to come together in a common cadence to produce working software in a continuously delivered fashion. Many times, these issues become so grave that the organisation reverts back to the Waterfall model that they came to hate, but at least understood.
This session explores Agile scaling concerns, and places particular emphasis on an architecturally significant distinction in the software to be created, and the components produced to allow the software to be created. That distinction revolves around cross cutting platform concerns versus product feature creation concerns. We will examine the distinctions and explore solutions that should help your organisation get past these issues when it comes to portfolio management, by paying attention to extrinsic versus intrinsic value metrics.
Watch this video on http://vimeo.com/user22258446/review/79095050/ead850f663
Presentation slides: http://software-architect.co.uk/pdfs/Howard_Deiner_Agility_at_Scale_Platform_v_Product_Concerns.pdf