I spent two weeks last month interacting with my business partners and friends about agile methods. They are curious to learn and introduce agile methods in their project portfolio. This post is to explore the reasons for their curiosity.
My friends and business partners whom I interacted with, are working in IT groups of large enterprises. They are responsible to deliver a portfolio of projects to business users. Their teams follow a homegrown customizable IT framework that comprises of stages and gates. For each stage, there is a gate or exit criteria. For example, requirements sign-off is a gate to ensure completion of the requirement analysis stage. The key thing is the budget approval happening at a certain stage, which is very important to execute downstream stages and stage-wise activities. In each stage, the team members create documents – some of these documents are to comply with the IT framework and in some cases, one or two extra documents are created to satisfy regulatory requirements.
Projects start, and projects end. However, as you guess, there are changes in requirements and designs at a later stage, and hence there are issues and teams pull it through to deliver the end product with some slippage. There is a dire need to optimize and demonstrate improvements in productivity as well as quality.
Agile Manifesto and Agile Principles are the foundation of Agile methods. In principle, Agile methods have the potential to help project teams deliver meaningful solutions in stage-gated IT environments. There are several reasons. Here are six of them.
There can be other reasons too. If you are working in an IT environment and follow a phased approach or stage-gate approach, what are your pain areas? What are the three reasons that matter to you most when it comes to introducing Agile methods? Let us discuss.
In my next post, let us explore how we can bring in Agile practices in stage-gated IT environments. Stay connected!