Software Delivery Life Cycle Delegation

Report

Use Software Delivery Life Cycle Delegation Levels to clarify who’s responsible for what items and subitems of the Software Delivery Life Cycle and to what level. This is a method where you can encourage software team member engagement through controlled self-organization.

The objective is to combine Software Delivery Life Cycle with Delegation Poker. You can frame delegating decisions and tasks within the Software Delivery Life Cycle to your team within a controlled environment. It’s a conversation topic about how to iterate through Software Delivery Life Cycle Delegation items.

In a meeting or async, a group who wants to align on accountabilities and responsibilities puts delegation level cards on the software delivery life cycle items or sub-items (one card per person). After placing the cards, they check the result. In case different cards have been played, the team starts a conversation - via Miro stickies or comments - or in a meeting about the specifics of the SDLC item/sub-item with respect to the delegation. You can also start a conversation in case the same cards have been played if that helps the team.

The conversation can go into estimation poker style: highest and lowest card players explain first what led them to play the card. You can also go round robin talking about the played cards. Important: make sure everyone is heard and can explain the reasoning why they played a card.

Categories

Lothar Schulz image
Lothar Schulz
Head of Engineering@Miro
A communicative, enthusiastic and dedicated manager with extensive experience of software development. Able to initiate projects and give new impulses. Proven leadership skills involving motivating teams to achieve their objectives. First-class analytical and problem solving skills. Able to adapt very quickly to fast moving and international environments, cope with pressure and set priorities. Loves to code.
Share your comment with the Miroverse community.

Similar templates