Profile cover photo
Profile photo
Geoffrey Dunn
360 followers -
Saving the world
Saving the world

360 followers
About
Geoffrey's posts

Post has shared content

Post has attachment
I took this photo a year ago and only now looked up who Kirobo is and why he's listed alongside astronauts and cosmonauts. He's a little talking robot the Japanese guy (also pictured) took with him
Photo

Post has attachment

Post has attachment
PAX 2016

Post has attachment
I found this a fascinating read. While I've never been a big follow of the Tuckman model I do think about how team experience needs to harmonise with individual experience. But even most of that research is from competitive sporting or similar teams that are not at risk of stagnation. So I now have another area to think about and look out for.

http://www.heidihelfand.com/dynamic-reteaming-is-inevitable-you-might-as-well-get-good-at-it/

Post has attachment
The age of Cyber warfare is now

Post has attachment
So I guess the church is against surrogacy? Weird way to announce it.

Post has attachment
I have mixed feelings about this article https://medium.com/xing-engineering/when-story-points-misfire-88b068bfc97c#.u4s87d99a

I've seen every anti-pattern example given in planning meetings over the past 3 years. And mostly I've just let them slide on by. I recognise them as issues and something that can expose some interesting misunderstandings. But if the estimate is "close enough" then I want the group to just move on.

Planning poker was invented as a strategy to get quicker estimation by allowing some of the design differences to be ignored (for now). If people agree on a estimate even if they do not agree on the implementation method then let's not spend time now talking about implementation. If someone estimates a 5 and another gives an 8 does it really matter which number we picked? Let's focus conversation on those times someone estimates 3 and another estimates 13.

What are your strategies with a team that wants to estimate all their stories? When is the conversation valuable and something you'll ask the team to slow down and discuss? When is there little value and you push them to just pick a number and move on?

The only anti-pattern I get specifically involved in is the last one. "I need an estimate". Great! What do you need it for? Is there a date already locked in? Who will this effect if it's late? How late is too late? We're pretty much just guessing right now you know that right? We can forecast now without an estimate. Or do you just want a rough idea of cost vs value?

That conversation is my favourite :)

Post has shared content
Could have helped the dude get his millions back

Is there value in having a test specialist within a team?

Testing is something that tends to be brushed over or pushed back onto the "developer" roles in the team. And while some, such as Lisa Crispin, are writing about the value a tester can bring to a team there are others who see Agile as somehow anti-tester.

What are you seeing teams do? Do teams typically have a full time tester? A part time tester? Just let the developers do it? Does the kind of work or team size matter?
Wait while more posts are being loaded