Archive for the ‘Agile Management’ Category
Tale of two SCRUM stand ups
Tuesday, February 2nd, 2010The first team was sitting down in a breakout area. Their body language spoke volumes. There was not one single participant maintaining eye contact with anybody else. Two people were playing on their phones. One developer had his head in his hands. Most had bored expressions. The team leader who is also the SCRUM master was the only person who spoke for the entire time I watched.
The second team was stood in a space near their desks. They were gathered round a task board which appeared to be up to date and the focus of several of the individual's updates. One person spoke at a time. Almost everybody appeared to be paying attention to whomever was speaking. Most updates were short and concise. A couple rambled on.
Other than both teams calling their meeting a SCRUM I could see no similarities.
As our agile adoption has spread beyond the original teams I suppose it is inevitable that as the experience gets spread a little thinner that people will simply label their existing activities with agile sounding names. Often we have no clear remit in those teams to supply a mentor and to try offer advice would result in rebuttal as team leaders guard their territory. Does this matter? Is there a risk that these teams who are not practicing agile correctly will diminish and discredit agile in the eyes of our programme managers? This is sounding a bit like an excuse for an Agile Inquisition going round checking that no team is using Agile's name in vain. This cannot be a good thing either.
Using JIRA for Agile Project Management (without Green Hopper)
Tuesday, January 12th, 2010Jira from Atlassian is a very popular issue tracking software and can be quite effectively used for Agile Project Management. Jira has a plugin (Green Hopper) that allows for creation of a backlog, iterations and tasks. However, with help from the free Mylyn plugin for Eclipse I was able to setup a Product Backlog and Iteration Backlogs.
For the User Stories in the product backlog I created two issue types (Epic & User Story). Story hierarchies can be represented using Jira Links.
For Iteration Backlog I created a version for each iteration and assigned the stories to that version/iteration. Each leaf story can then have Jira Sub-tasks to represent the tasks in a particular iteration. The Resolved state of the story is used to mark it complete and Colsed state is used to mark it as “accepted”. You can use Mylyn to see story hierarchies, also I found Mylyn to be a much more intuitive interface when working on Product and Iteration backlogs.
By Mashooq Badar.
As a manager define outputs, not process
Tuesday, September 22nd, 2009Ask for consistent outputs, not consistent processesThis is a big leap for many managers and senior stake-holders. I worked with a team recently who had been told to do daily stand-up meetings. They were told that each must answer three questions (you know the three, what yesterday, what next and what’s blocking). The teams manager had a team member minute the meeting and send him an e-mail to save time. I was asked to have a chat with the team about why they seemed unhappy with this new “agile” approach. The first step was to invite the manager to write a contract in terms of his information requirements and agree that so long as the team could fulfil the contract he would accept their approach. A short retrospective later and the team are posting key information on a board for all including the manager to see, the minuting of the meeting has stopped and they have taken back their stand-up whic it turns out they quite liked now it could move faster without minuting. So thanks for the reminder Liz and thanks for sharing.
Ask for consistent outputs, not consistent processes
Read more at lizkeogh.com