Quote on this page: In the past we separated business, IT change and IT Operations, in fact we created islands and silo’s. DevOps stop this mind-set and behaviour.
Comment to above quote: If you still have separate departments: IT and Change... that's a thing to solve.
The soner the better.
If you implement Scrum it does not mean you are Agile. This culture change is not that big for employees (the teams will love this way of working), The greatest step is to be made by management. Self-steering teams are different, It will ask for different governance and a change of the management culture. Switch from steering to facilitating the teams. The teams takes the ownership of the change. It is very productive, quality software, less incidents and fits into my beloved focus in the field of efficiency, optimization of work processes, flexibility and reaching concrete results. But it is the team if a story is ready for Sprint. Is the story clear and analysed on what to build, test and delivered. If the story is too big for 1 sprint the team makes the decision where to scissor the story (to realized it in more than 1 sprint). The Product Owner owns the Product Backlog and is responsible for the prioritization.
Prioritization does have 3 parameters:
The Scrum process is simple to understand, and it will bring you great productivity grow. Increase of productivity is only the first step. You need to grow into maturity and automation.
If you implement Scrum it does not mean you are Agile.
Scrum team delivers:
DevOps team delivers:
Issues during transforming
Be aware that in the DevOps world there will be impact on roles like Project Managers, PMO's, Quality assurance and Business Analyst. There could be some redundancy.
Copyright @ All Rights Reserved