In Cranked we have just two roles, Business and Technical. Compared to some other software development methods, this is a very small number. So why are there so few roles? There are two main reasons for this number. Reason One If work is passed from role to role in sequence, then there are hand-offs to … Read moreReduce Roles and Reduce Handovers
When we documented Cranked, we included just two roles: Business Technical That’s it. Just the two. This isn’t actually very controversial; it is simply the next step in an evolution of roles – as shown in the diagram in this article (you can click through to a larger version). The essence of the diagram is … Read moreEvolution of Roles
If you have read our book on Cranked and want to read further on the specific topics, the following map shows a recommend set of books that offer great insight into the fundamental aspects of Cranked. The reading list works from the centre outwards, and you can work out along each node to find out … Read moreCranked Reading List
Welcome to Cranked – a framework with an example implementation; a sequence of stages, activities and practices that draws inspiration from many lean and agile sources. Craftsmanship Reduce Waste Agile No Estimates Kanban Extreme Programming Drip Funding / Deploy Continuously The Cranked framework seeks to dramatically reduce the feedback loop by helping teams to quickly … Read moreWhat is Cranked?