In this article, I am going to explore how projects can be successfully delivered when there are multiple stakeholders and multiple streams of work a.k.a work streams. I use the work streams intentionally here, even though it is a significantly overloaded term and varies across organisations. In this context, it is a logical grouping of business value improvements, activities and tasks so that they can be managed appropriately and any expectation met. As our teams develop and work on larger and more complex projects, these different groups need to complete a continuous but progressive list of technical tasks. These tasks are grouped by whatever domain ontology is pertinent to the project and yet deliver the customer centric, business feature. For example, for UK's leading organisation that help save money by comparing a range of insurances, a cross-functional squad of engineers regularly delivered the aggregation engine theme of work, another squad delivered the client services that consumed various systems and this was all unpinned by a DevOps squad that delivered the continuous integration and continuous delivery strategy. This is how we aim to deliver all projects and forms part of Cake's software delivery process model.
The main basis is around reducing waste