Slicing & Value Driven

Food for thought

Every time I watch my kid eat cake — it make me nervous inside. Almost killing me, sometimes. But the truth is — the one that matter is my kid, not me. As the eater, he is in solid position to decide how he want to enjoy the cake.

Last Friday I was on a call with one of my Lead Engineer. He briefed me that he used the technique of “one engineer per user story. He & his engineering team agreed to practise that way to maximise the value of their Sprint. Less dependency on other people. Exposure of different layers.

When I build the team, I know that I want it to be SCRUM team. & I hire full stack engineer. Even at the moment the new team member is hired he/she not yet a full stack engineer — but the objective is clear.

In a SCRUM, the team should be capable enough to deliver a workable deliverable (value). This is where the slicing require a full stack or the combination of all — create the full stack.

Upscale & downscale friendly — in the event where we need to downscale the team due to whatever reason (budget, VC pull out money yada yada), the team can still function as they (they as in “individual or a combination of individu) are able to work at each layer of engineering including front end, back end & infrastructure.