If in a predictive approach

I've run small to medium projects in a similar manner. I became a CSM in 2007, but it was several years before I worked in an organization that used Scrum, so I borrowed from it wherever I could. One important thing I've learned is that agility is more important than Agile.

On a side note, watch out for third party implementation partners who say they are using an "agile framework" but are really just applying a 2-week readout cycle to a predictive process. Buzzwords and branding don't improve performance.

- Greater awareness of project status and challenges
- Better requirements and design
- Improved knowledge of and support for what was implemented

Luis -

Many tools and techniques are life cycle agnostic - they can be applied to predictive and adaptive life cycle projects equally well.

Putting lipstick on a pig won't change its genus or species...

Kiron

Hi Luis,

I would take @Kiron’s use of the word “agnostic” even further and say that:

- [A] All delivery approaches are templates, [B] PM’s are content managers, [C] combine the two, and you have a tailored project to meet the needs of your customer.

Under this way-of-thinking, one does not give a name to a delivery approach, although you could generically call it “Hybrid.” Obviously, this mindset is “fighting words” for many, as there is soooo much emphasis on specific practices/approaches/methods/lifecycles/mindsets, etc., but in truth, I think the “no name approach” is aligned with the dictates of our profession.

Dear Kiron
Thank you for participating in this reflection and for your opinion

I would like to better understand your comment: "Putting lipstick on a pig won't change its genus or species ..."

In other words, using agile techniques with a predictive life cycle or waterfall techniques with an adaptive life cycle does not change the pros or cons of using that life cycle.

Kiron