Using agile project management methodology has is own pros and cons. At many large enterprise organizations PMO or Head of Projects force project divisions to adopt to agile, scrum or kanban.
To support this action they send all their PM’s to classroom trainings, to conferences to make sure that they can apply the best tools and apply best in class lessons learned from industry.
Question is very simple, why organizations fail to adopt Agile project management methodology?
If you don’t have enough expertise, you should try to hire the best vendor possible. What characteristic your vendor should have? Number 1, vendor have to understand your company culture and how you operate. On all successful projects vendors and clients are working together really closely. Many cases people from each team are colocated to make sure business requirements are close to “perfect”.  Planning take place together, agreement of sprint duration is curtail, which most cases vary between 2 weeks to 5 weeks. As recommendation, I believe 3 weeks are most sufficient whereby 2 weeks are allocated to development and 1 week for testing.
Vendor have to be flexible to make sure they stay transparent, adaptable and well-established. Criteria’s may sound obvious but in many cases they are the platform of confusion and misunderstanding. And if misunderstanding starts it will cost you more money and schedule will increase.
Organizations should have a clear solution which means time spent on investigating the right solution. It may sounds to much time or money spent in the first place but it will be all payed of in the end.
Key learnings:
Agile is a mindset
• Make sure you focus on to get the right answers as soon as possible. – e.g.: How can I get the information I need earlier? How can I start development earlier?
Use agile vs traditional methodology
• Taking acceptable risk – e.g.: analogous and parametric estimating services add huge amount of value and increase efficiency/effectiveness
• Try to bring project deliverables forward if sufficient information is available.
Agile can prevent miss-understanding/recycle
• Need to clarify scope early – e.g.: work shadowing can significantly improve requirement gathering and quality
• Identify show-stoppers early
Marketing – Sell the benefits of the process
• Business need help to understand what agile methodology is all about. You should expect positive outcome and smooth integration between business and IT.
• As soon as they are involved they are keen to know more.
• You need to manage expectations on the right way.
Need a strong change management process
• User change requests need to prioritized against existing development plans.
• Strong process for completing dual maintenance
• May need some agreed change moratorium periods
Easier transition to support
• Removes the spike in system issues and support associated with big-bang approach
• Iterative approach ensures support processes are fine tuned during project execution