Click to edit Masterproblem text styles A real life analysis scaling Our learning is based on working on a large scale agile project that had the following characteristics: • Largest online retailer of train tickets in the UK • 250 member team with planned rotation. Single code base
Click to edit header • Distributed across London, Bangalore, Pune • Productize the solution, to allow multiple tenancy • Cross-channel sales capabilities
Goal: Replace a legacy system with a new platform that provides the capability to add new features quickly while the product needed to continue with planned revenue generation
Click toto edit Master text we styles What happens Agility when scale? Planning Aggregation of work across streams Depth of knowledge and Involvement in dev process Scope creep and/or system gaps
Click to edit header Communication During release initiation meetings, virtual conferencing leads to inefficiencies Frequent face-to-face communication adds to project expenses
Click to edit Masterfor text Sustaining: What worked usstyles JOHN’S BUCKET
SWAT TEAMS
Click to edit header
REPORTING
Features
Feature Completeness within Milestone 3 UK Beta Site EMT enhancements SEO Industries In-line styles migra on Search Archive Ar cle Feedback forms DPA preferences Liveflo Topic Migra on Analy cs Security Display ar cles from Tracked Topics Saving Searches SME Insurance Educa onal users Authors Custom Add on Add ar cles to Favourite items Recruiter Benchmarking Legisla on Performance Subscribe Legal Advice Home Page User Funnel URL Migra on Tools general Ar cle Migra on
Click toto edit Master text we styles What happens Agility when scale? Team organization Unmanageable team size
Ad hoc overlap of responsibilities
Loss of ownership
Teams re-organized based on system layers split or feature based split Team composition Support teams for NFRs, release mgmt., Prod & Operations support
Click to edit header
Continuous Integration
Infrastructure & automation
Components Dependency issues
Deployment Overheads Maintenance of different product versions
Development practices – code reviews, technical assurance, refactoring work items, rigorous test coverage
23
Click toto edit Master text we styles What happens Agility when scale? Planning Aggregation of work across streams
Idea generation with business case template
Depth of knowledge & Involvement in dev process
Concept Triage
Scope creep &/ system gaps
Release Planning
Click to edit header
Team Iterations ID, DD/ inception
Communication During release initiation meetings, virtual conferencing leads to inefficiencies Frequent face-to-face communication adds to project expenses
Click to edit Master text styles Takeaways • Shared vision and understanding across the program – Release Kick offs, Feature kick offs • Overall product stability with increased collaboration across dependent features and external dependencies • Immediate revenue generation from the revised product while having Click to edit header stakeholders collaborating at a desirable level • Team BAs and Development Managers – redundancies, developing fool-proof solutions, removing bottlenecks, increased product understanding
• Data analysis benefits for studying industry trends & user dynamics
