Skip to main content

The way our team's work week works



Our normal work week is currently organised like this:

Monday morning, and the #weeklyStartUp

We start the week with a short 15 minute meeting the whole team (20 people) participates, called "The weekly startup". In that meeting we go briefly through our main goals for the week, and decide in which kind of work groups to solve them. People can themselves decide which goals they want to work with, and based on that we decide our work groups.

This goal list is a one page google doc with 5-10 goals, each written in the format of Do what, in order to get why accomplished.

And the goal list is not meant to include everything anybody is going to work on, just the most important goals. We allow and expect people to engage on various other things too, as long as those won't come with a big expense on the main goals.


Monday-Thursday, we work

Work groups have full freedom and responsibility to plan, implement, test, deploy, and communicate what they believe is necessary to accomplish the goal. I usually encourage each group to:
- create a high level plan of what steps needs to happen so that their vision is fulfilled
- visualize and track work in progress in their preferred tool
- do some mob programming OR then sync often

And we have a set of common ideas for group work.

But in the end it is up to each work group to decide how they want to work.


Friday morning, we #showTheTeam

We have a 1 hour meeting called showTheTeam (STT) that is optional but still each team member participates into. Here each work group shows and tells how the goals have progressed, plus anyone can freely show anything else they have done or learned during the week.


Friday afternoon, some #prePlanning

We have a ~1 hour meeting where we try to come up with the goal list for the next week's startup meet. The meeting is also open for all, and usually about half of the team joins. Here we will discuss and debate what we should work on next, with the help of a google doc we call "The list of things", plus people chipping in with other things they think should be done next.


Weekend

Have fun!

And maybe write a blog post...


Comments

Popular posts from this blog

Periodical retrospectives are lame

  "You got nothing, not a single thing?! Well lets just end this here then." I remember well when I said this, being very frustrated. About ten years ago I had been working as a Scrum master for a team some months, and putting quite a lot of effort into planning our scrum teams sprint retrospectives. Lot of work also because I felt we were not getting too much out from them; not very good discussions, very few actions, and even the few actions we did come up with did not stick.  And then it happened: a retro where none of the participants came up with anything to say about the sprint. Regardless of the retro topic boxes, reading of books on retrospectives, getting inspiration from tools like retromat.org, having them in different places, using all kinds of different formats and rainbow coloured post-it notes. Not a single thing. Blank.  So then I said the words, out of frustration, mainly to myself. Why couldn't I get this thing everyone is so hyped about to work? Af...

Testers doing test automation - is that the most important thing for you to do right now?

I've been thinking quite a lot about tester's moving to do test automation.  Lately beause of these three things: 1.  European testing conference , a great testing conference I attended couple of weeks ago. It is very cool due to many things; the way the speakers get compensated, the focus on the conferring side of conferences making it very easy for people to discuss stuff, the way the talks are chosen, and because there are also a lot of developers joining. So anyway when I was talking with several of the attendees, it was a bit strange how it was easier for me to talk about the product development as a whole with the developers, where as with the testers it more naturally moved into talk of automation and tools. Also on the open space, I think the majority of the topics pitched was automation or tool related. And quite little on the process or on the customer facing side of product development.  2. In my company there are a lot of different products and...

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.