All hail the story wall!
On agile project teams the use of a story wall is ubiquitous. It’s an asset that shows all of the stories (requirements, pieces of work) in play, and their status. It’s a physical wall (often with a virtual counterpart) designed to be an information radiator.
Nobody owns the wall, everybody can contribute to it. That’s the theory, at least.
On many projects the PM and BA are the main consumers of the wall. Their day to day life revolves around it. This leads to the impression that they, in fact, own the wall and an odd culture of taking permission to make changes emerges. I don’t really like it.
Yet another great Chrome plugin, folks! Roll up! Roll up!
By default, the basic version of Trello exports data to JSON. I don’t now about you, but that isn’t too handy for me as I use Excel/Numbers/Libre Office so along comes the Export for Trello Chrome plugin.
Install and activate the plugin, and now when you click on the ‘share, print, and export’ link in Trello you’ll see an option to export it to Excel.
Job’s a good’un.
For most of 2013 I was working as a programme manager on a large engagement for a retail bank, in their network operations and projects area. We handled new project work of all types through two teams- a ‘BAU’ function and a rapid response projects team.
What kind of work did the team undertake, and where from?
When we set up the projects team things were going well. The client liked it because they were able to get risky or more urgent work estimated and worked on much more quickly, accepting a project management overhead that wasn’t there with the BAU team.
Things started to go sour, though.
Today marks the end of a very unique project. It’s not necessarily the aim of the project that is special, but the mode of engagement; one XD and one BA for 2 days a week for 4 weeks to revamp the header of a website. My first thoughts were, what can you do in 8 days?
It turns out, an awful lot. I’m putting together materials for our final showcase and there’s way more here than we could reasonably fit into an hour slot. In this post I’d like to share how we approached the time challenge, some of the activities we undertook, and what kind of outcomes we’ve seen.
The last month has been spent working with new people, on new things, in new ways. It’s been a great experience, but no great learning is complete without a little retrospective and internalisation of what’s happened. Interestingly enough, though, I have learned a lot more about running a waterfall project better than I’d expected.
Here’s a few thoughts..