The 6 commandments for a successful iterative and continuous delivery approach
26 October 2015 |
Sandra Falque | About a 2 minute read
Developing a product using traditional IT project delivery methodology can sometimes have a taste of travelling through an endless tunnel for the product team and of putting money into a black hole. You don’t see what the outcome will be until it’s too late, where expectations are often not met.
Our experience helping leading organisations in implementing new ways of working combined with our work with Stuart, our highly experienced Delivery Head Coach AND Pragmatist, helped us identify 6 stages to evolve from traditional waterfall delivery to an iterative and continuous delivery approach:
1.Thou shalt be Agile:
Quicker development of product, higher success rate, lower costs, higher motivation. There is no need to boast about the benefits of this not-so-new methodology which has recently become one of the hottest buzzwords in the IT development industry. Building a co-located self-organised team will have a major impact in delivering to expectations.
2. Thou shalt automate tests:
Giving all the testing responsibility to dedicated resources can be very time consuming and lead to misunderstandings. In an ideal Agile team every developer should be able to write tests and tests should be automated to achieve both Continuous integration and Continuous delivery.
3. Thou shalt do BDD:
Because BDD(Behaviour Driven Development) forces the discussion around the requirements and improves understanding, doing BDD should mean less testing required at the end (due to more automation) and better shared understanding for requirements
4. Thou shalt involve the Product Owner:
Who has never experienced the damages caused by a lack of communication between the development team and the business? Waste of time, money and effort, barrage of change requests, demotivation. Having a Product Owner in the team from day one not only will give business owners the ability to see how the team works but more importantly it should enable to build quicker a product that is closer to business needs.
5. Thou Shalt have DevOps:
Currently there is a split of responsibility between Developers and Operations people (and they are not part of the same team). The DevOps should add context to the people that are carrying out the Ops changes and be a tremendous help to build environments and deploy quicker –achieve shorter release cycles (hours ideally) should be their aim.
6. Thou Shalt embed Service Management:
With level 2 service managers (ITIL Problem Managers) in your team from day one, you will save a lot of time training and up-skilling them, achieve a faster and better resolution of service and increased trust between and across all functions
Questions? Comments? Remarks? Willing to go further? Contact our Professionalising Digital team ([email protected] Digital.com) to understand what is new with each of these recommendations, what are the pitfalls and level of priority and how to implement them in your company.Read More From This Author
Tech Lead (Reading)
Bring your expert tech knowledge to the table to influence the direction of projects, whilst coaching and your team through engineering best practices.I'm Interested
DevOps Lead (Reading)
Bring your delivery expertise to the table, leading the pack as ambassador on operational requirements, influencing and continuous development.I'm Interested
Programme Lead (Edinburgh)
Bring your expert project knowledge to the table to own delivery of all our initiatives being delivered out of our Delivery Engine.I'm Interested