Recently we encountered a large-enough issue that required a postmortem (like a retro). One of the teams involved asked if they should put that into the sprint and give it points (ie. size it). This reminded me of a debate we encountered in our earliest days of implementing Agile.
One side insists that we only
I thought I'd highlight the milestones SendGrid has had in our Agile journey.
When I started at SendGrid in May 2011, the organization was on the verge of adopting Agile and Rally's agile software solution. In other words, the decision to move to Agile had been made prior to my start. (In fact, it was
Introducing the newest meetup: Agile Coffee - OC.
I've been meaning to start this group since Stuart & I went up to San Fran for the SF Agile conference last May. There we met Jim Benson (Personal Kanban) and were introduced to Lean Coffee as a forum for discussing Lean, Kanban, Agile, limiting WIP, visualizing workflow, and
By our Agile cadence at SendGrid, team retrospectives (and demos) fall every other Tuesday. Today one of my teams is coming up with a focused set of actions to try to solve the problem of distractions / context-switching.
This team deals with many of our system-critical services (mail processing and delivery), so it's staffed with really smart
With the new year comes a fresh new crop of initiatives targeted for the upcoming twelve months. And those initiatives ain't gonna drive themselves to completion. This is where the project manager / scrummaster steps in resolutely and takes control.
First, the tech leads of each team get together with the SMs and POs and hold a
Agile coffee, indeed. I've had no fewer than three cups today.
Resolutions for 2013:
no more discussing coffee, today
make most of Mike Cohn's day with us
talk through my retrospectives at SendGrid
get out into the community talking about agile principles
OHIO - only hit it once!
That's what's brewing. Let's make 2013 our