DevOps mindset

Agile DevOps, the mindset and the pitfalls

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.

Agile DevOps


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:

  1. Business value
  2. Risk
  3. cost of delay

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.


DevOps

If you implement Scrum it does not mean you are Agile.

definitions:

Scrum team delivers:

  • analyses, build and system test
  • use the scrum process

DevOps team delivers:

  • Analyses, build, tests, including user acceptance test support
  • implementation in acceptance and production
  • Functional Application Management
  • they build it and they run it
  • use the scrum process


Issues during transforming

  • Not every employee (especially Project Managers) from the classic world can easyly transform to the new way of working.
  • they still think in projects, PPD's and PID's. things are chinging here as well.
  • PMO still asking for planning, resource management and timewriting. also here we will see a transformation. Also in this area is the question: "what do we need in this new way of working"
  • One of the characteristics of Scrum/DevOps: team is fixed and the cost are fixed.
  • Resource management between teams. Don't do this. Think in Stories and if the resource who can do this is in another team, go to the ProductOwner of that team and ask him to put your story on the Product Backlog of this team.
  • There is a need for technical coordination between the teams. In detail focused on interfacing between the applications. This is the Integrator role.
  • There is the need of a Business Consultant at the Business site. Select this Business Consultant (together with the business), arrange adequate training and move this person to this Business floor.
  • The team does have the goal to 'build it (IT) and to run it (IT)'. take care that every member in this team can take several roles. Take care of the education and training. The team should have the capacity to do their own analyses.

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.

RIEKELT PASTERKAMP



Management Drives: Oranje / Geel

Copyright @ All Rights Reserved