7 Followers
17 Following
27 Posts

Pied piper of software development; true full stack from embedded bare metal to cloud and everything in between. Currently leading all software development at Blink.

All opinions here are my own.

Inclusion makes us all better. Climate change is real. Tacos and sushi are proof that we live in a good world.

@luxalptraum and by crawl I mean Santa’s trying to get to the next bar while not being chased by the zombies. If they were caught, they became zombies.

@luxalptraum I think the OG santacon was actually a santas versus zombies bar crawl in Boston/Cambridge.

Only there were nerf guns.

@DrJekyll I like some things of SAFe: notably the focus on the north star, slightly longer than a sprint planning and BRP can be a great thing for hybrid/remote teams. The hyper focus on work priority and the space to create left open for the teams.

What the SAFe group added though - the overhead and process - is designed to get in the way of delivery (in my mind). I think I lost count of all the roles they've added!

I'm assuming your experience was with 10-20 teams?

@DrJekyll I have issues with SAFe, but modifying it and reducing the process and never hiring a safe consultant can work.

@kironbondale i wasn’t even thinking of the scrum guide/master in my comment and that’s a great add! Though, to be fair, when I’ve been at companies with dedicated scrum guides, that’s when I’ve seen the worst of the “the ceremony is the only way” mentality.

This gets into how i like to staff teams to ensure scrum, po, and manager have enough scope so they can’t default to micro/focus on process for process sake.

@Crook I bet! It's so common and goes against the manifesto.

What really gets interesting, with regards to learned helplessness, you'll find teams accepting 2+ hours of stand ups and 2 out of 10 days of ceremonies and then hours of backlog refinement as standard. That is a lot of process - with diminishing gains.

Those are always the fun challenges. Particularly for me as I'm typically well outside the daily operation of the engineering teams.

Scrum by micro management leads to learned helplessness (LH).

LH kills software development and innovation as the team learns that "someone else will do the work defining every step". This leads to 'leaders" stepping in more to micro.

My tl;dr on how to break this pattern is give the team the mandate and the space to fail. Repeatedly. Also, get the person driving to give up control. Most of the time, they don't want that control. This tl;dr has a lot of sub parts and it's never easy.
#agile

@larsibacken thank you! I love putting a new camera in it's paces. image stabilization these days is amazing!
@victorwynne no, but I grew up going to NYC all the time and still try to get down there 1 to 2x a year.
@victorwynne I can’t make it out, I plan to Google shortly