From wiki
Jump to navigation Jump to search

Can we add some stuff to this page, in particular - I would like to expand on DevSecOps CI/CD and its details. I just did a large project plan and business case which incorporated DoD's DevSecOps which is a fantastic comprehensive framework - of course scale accordingly (to the size, complexity, criticality of your project/product development cycle) and DORA are we there yet? where are we now and what are we aiming for? thus, Agile maturity models are important. As so many depts now chase chaos, fighting fires, with massive silos (knowledge is power/control), and a heroes welcome to saving the day... maturity model -1000+ 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. Good luck with that... 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.

Then comes the organization culture, people, process, governance and tools which is important. Need buy in at every level or something will merely fall to the ground in waste.

this is good -


Projects I have been on that were a success: Evolving 600 user stories from key SMEs/stakeholders using focus groups, surveys, and continuous feedback. Evolving key scenarios to prove the concepts working with the field units empowering staff, adhering to the laws of each province, building small correcting mistakes quickly iteratively with prototypes (Boeing failed building iteratively with many prototypes/proof of concepts, with key SMEs in the loop and a good baseline of requirements (from defense research), with good people, tools, process (achieved CMMI level 5) with direction, commitment, goals, small builds

Projects that were a complete failure (I didn't stay on these messy projects): lacked a baseline of operational requirements (client’s needs) for critical/complex projects a baseline of requirements is important to determine if you are meeting the client’s needs, priotization, risks and scope will be all over the place and cost…throwing money into an endless firepit.