Quote on this page: I am a Agile adept. What not means Prince2 projects are a bad thing. Until recently I was in several project boards. Agile way of working simply more flexible, better pace of change, etc. You are much more and better in control using Agile/Scrum way of working.
In the past I have seen several attempts to close the GAP between Business and IT. The last one I have seen in project way of working was CMMi. On maturity level 2 you will find Requirements Management and on maturity level 3 you will find Requirements development. Requirements development, together with the business is most important, including the signed off the requirements.
The issue here still is that the IT department still right down the requirements. It is there interpretation of what the business wants to achieve.
Agile way of working is another attempt to close the GAP between Business and IT. What is different this time? Business is writing down the Story, there will be story mapping. And of course the Business needs some help. That’s why I suggest to have Business Consultants on the Business site. They should be part of the business, they would make (as part of the Business) the stories on what IT should enable the Business grow.
Prioritysation will be done by Business stakeholders and is based on 3 components:
Suggestion to read:
Pearson Education User Stories Applied
Education is always very important to get to an higher maturity level.
In the transition to Agile/Scrum/DevOps it is mandadory in every step and for every employee.
some samples what should be available in this transition:
In my whole career I never have seen processes reinforcing each other as I see it today.
2nd quote on this page: How many paper do you need to change 1 line of code?
Let start thinking of that question, please.
There nothing wrong with waterfalls. But I love the above one the most.
Copyright @ All Rights Reserved