… getting more stuff done
At Trade Me we want to measure the overall health of Tech (that’s our team of 125 designers, developers, testers, BAs, and Squad Masters) to identify trends and to know if we are getting better (or worse!). We know that when we measure something it is a strong way of saying “This matters” which is why we put a lot of effort into deciding which metrics to collect.
So, you want to choose some teams? Well, you came to the right place… Many people have asked us to share our run sheets and material for the self-selection sessions we have run during the past years. So, by popular demand here’s what we call the...
Spotify’s whitepaper on how to structure an organisation with Agile tribes, squads, chapters and guilds has been the most inspiring and interesting idea to come out of the Agile scene in the past three years.
Organisations get the best results when people can choose what they work on and who they work with. In that spirit we decided to let people self-organise into small, cross-functional teams called squads. Up until last week we had six established squads within two tribes the rollout...
... let teams self-select! At Trade Me we’re in the process of getting everyone into small, cross-functional teams (squads) that will persist over time and across projects. Up until last week we had six established squads and the rollout had been purposefully slow and controlled. Now we felt...
Why your daily standup should be driven by a daily goal
Let’s face it, the daily standup can be a boring affair. I’m not talking about abominations with 16 people or half-hour long status reporting meetings. I’m talking about the ones that are kind of okay and adhere to the rules but nonetheless are a bit boring and lack focus and enthusiasm.
What is a premortem?
A premortem is a project postmortem that’s run before a project. During a postmortem people analyse and discuss what went wrong, what went well and what could be improved.
While postmortems are very useful the problem is that by the time we run them the project is usually over and not much can be done about success and failure.
Hi, my name is Simon and I am a Project Manager at Trade Me. Sandy kindly asked me to contribute to her blog, and I consider it a great honour. Below is my story about how we embraced Agile to inject magic into our project.
Last week Jan, Mike, Anthony and I were at Agile Australia in Sydney and had an incredibly good time. The conference turned Twitter handles into people, exposed me to TimTam slams, and taught me that Beyond Budgeting is not a boring accounting thing but a riveting management philosophy.
Many novice teams find it difficult to strike the balance between too much and too little detail when writing user stories.
In the spirit of closing 2012 in style here are our 6 most popular blog posts written in 2012:
It is the time of year for winding down and reflecting on things before heading off to the beach for some BBQ-ing, drinking of things and general relaxing. So we wanted to thank you for your custom and support for 2012, wish you all the best for 2013 and share some of our reflections (we can share drinks and BBQs too, but that comes later).
A while ago I wrote about Personal Kanban at Snapper. Personal Kanban, or KanbanFor1 as we call it, has supported Snapper’s Agile adoption and has proven an excellent training ground for the team to develop good habits and behaviours.
As in all Agile adoptions the delivery team aren’t the only ones affected by the change and in this post I describe how I have used personal Kanban as a co-coaching tool to help a Product Owner adapt to the challenges of his new job.
I really like Jonathan Rasmussen’s project inception deck as a simple, quick and cut-to-the-chase way of kicking off projects. Overall, I pretty much stick to Jonathan’s content and flow, but sometimes, I use a press release exercise instead of a product box. The idea of refining a product vision through writing a press release has originally been used by Amazon.com as a mechanism to determine whether a product or service should be built.
My client, a New Zealand government department, is in the process of introducing Agile-Lean. They are currently in a trial phase to see if it is for them and during the early stages they’d like to run Agile and non-Agile projects in parallel.
Fair enough, but how to choose whether a project should be run Agile or Waterfall?