Changes

How do you know where to go if you don't even know where you are now... need a sense of direction and strategy/map.  Thus, a maturity model helps one aim towards some goal.

How do you know where to go if you don't even know where you are now... need a sense of direction and strategy/map.  Thus, a maturity model helps one aim towards some goal.

 

And, lets talk about '''requirements'''.  Everyone thinks that - we're Agile! we don't need requirements cause the client/SME/stakeholder is right beside us every step of the way.  But, we all know in reality getting the time/resources at the time you need key SMEs/stakeholders can be a challenge. (ref https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/5832/A-Business-Analysts-Experience-With-Scrum.aspx )

And, lets talk about requirements.  Everyone thinks that - we're Agile! we don't need requirements cause the client/SME/stakeholder is right beside us every step of the way.  Good luck with that...

[[File:Req analysis.png|thumb|req_analysis]]

[[File:Req analysis.png|thumb|req_analysis]]

I have been on many many projects.  Sure some don't require elaborate requirements depending upon the size, complexity, criticality, scope, costs, resources, experience/wisdom/knowledge etc...  but many do - at least a baseline of SMART requirements which evolve. The best projects I have been on have been iterative, incremental and iterative in approach involving key SMEs/stakeholders producing prototypes and proof of concepts with a SMART baseline of requirements which evolve with time to manage scope, costs, resources, schedule, quality, risks...  

I have been on many many projects.  Sure some don't require elaborate requirements depending upon the size, complexity, criticality, scope, costs, resources, experience/wisdom/knowledge etc...  but many do - at least a baseline of SMART requirements which evolve. The best projects I have been on have been iterative, incremental and iterative in approach involving key SMEs/stakeholders producing prototypes and proof of concepts with a SMART baseline of requirements which evolve with time to manage scope, costs, resources, schedule, quality, risks...  

Without requirements where will you start. Requirements allow you to prioritize, categorize, trace, realize, measure/monitor/correct accordingly and continuously and risk assess.  I've been on projects where scope was all over the place, so were costs and resources were heading in every direction with no one at the helm.  Requirements were no place to be found and the project was spinning in the mud for years just blowing throw money as though it was candy... a mess built an empire on the mess.

Without requirements where will you start? Requirements allow you to prioritize, categorize, trace, realize, measure/monitor/correct accordingly and continuously and risk assess.  I've been on projects where scope was all over the place, so were costs and resources were heading in every direction.  Requirements were no place to be found and the project. A baseline of requirements which evolve provides direction.

Then comes the organization culture, people, process, governance and tools https://www.compact.nl/en/articles/continuously-improve-your-agility/ which is important.  Need buy in at every level or something will merely fall to the ground in waste.   

Then comes the organization culture, people, process, governance and tools https://www.compact.nl/en/articles/continuously-improve-your-agility/ which is important.  Need buy in at every level or something will merely fall to the ground in waste.   

 

[[File:Devsecops culture.png|thumb]]

this is good - https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/5832/A-Business-Analysts-Experience-With-Scrum.aspx

ref

ref