“Agile” is a philosophy, a theory and a framework, which mostly suits to an incremental product development using a self organized and a cross functional team to deliver incrementally in an iterative fashion. This theory is based mostly on 3-4-5 Rule.Fundamentally there are 3 roles, 4 ceremonies and 5 artifacts in an agile practice like Scrum. It runs in a small cycle each fixed length called “Sprint”.
3 Roles: Scrum Master, Product Owner, Delivery Team
4 Ceremonies: Sprint Planning, Sprint Review , Sprint Retrospective and Daily Stand Up
5 Artifacts: Product Backlog, Release Plan, Sprint Back log, Burn Down / Burn Up Chart, Agile Project Management Tool
However, we can see an extension to this during a real time projects. Extended Roles: Extended Product Owner / Proxy Product owner, Agile Coach, Product Sponsors, DevOps specialist, PMO etc. Similarly extended Ceremonies like Product Backlog Grooming, Portfolio Dependency & Risk Management , Pre Planning, Release Plan, Distributed Scrum Meetings.
|C||Scrum Master||Sprint Planning||Product Backlog|
|C||Product Owner||Sprint Review||Release Plan|
|C||Delivery Team||Sprint Retrospective||Sprint Backlog|
|C||—||Daily Standup Meeting||Burn Down / Up|
|E||Extended PO||Backlog Grooming||Sprint Metrics|
|E||Agile Coach||Dependency Meeting||Risk & Dependency|
|E||Sponsors||Release Planning||Stakeholder Reports|
|E||DevOps Engineer||Pre Planning Meeting||–|
|E||PMO||Cross team meetings||–|
Success factors –Pre-Conditionin adopting agile
Essentially, Scrum framework can fits to any kind of projects. Project can be either a new Development project, or can be a maintenance or enhancement project. In all cases scrum framework can work well. However, certain practices like extreme programming need a stable environment and matured agile practices. However, we can consider few best possible scenarios where agile frameworks best fits are as follows:
Leave Traditional Approach…Adopt Agile !!!