When I used to be a freelance front-end developer, I remember working on a campaign site with a team of four developers. It was supposed to have an interactive 360 degree viewer up top that allowed the user to explore a set of rooms with hotspots and the like. One developer had quite a bit of experience with that sort of thing. That is why we split up: he would build the interactive thing and the three of us would build the rest of the site.

Often times the overall pattern for work assignment goes something like this:

This is pretty much the single most important thing to do. No, really — this is what makes all the difference. It’s about creating business value, team efficiency, motivation, everything.

  • well prioritized — most (business) valuable user stories up top
  • regularly refined — shared understanding across the team
  • thoroughly reviewed — transparent to stakeholders and kept up-to-date regarding new insights
  • ready — as in: the upcoming…

I have attended two Scrum trainings with Jeff Sutherland aka. Mr. Scrum. And each time he came up with the “11 ways to double velocity” part. And I was like: how could that ever happen to be true?

It’s done pretty quickly: crank up your calendar tool of choice, add a new event, throw in a bunch of your colleagues. There you go. You just created a meeting. And maybe a mess.

Looks pretty straight forward. Start the day with a Daily, end it with other meetings.

Mark Rickert

Curious dude on the agile journey

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store