Project Management..

Project Management..

So who needs project management?

Everybody!

Ger Hartnett (far right) of CoClarity says so – and I couldn’t agree more. He knows a thing or two about project management and we covered quite a few techniques from Get Things Done to Scrum.. which I have to say I like and fits in what we’ve being doing.. but just didn’t know it.

Bits from Wiki and Ger:

Scrum is an iterative incremental framework for managing complex work (such as new product development) commonly used with agile software development. Though not an acronym, some companies implementing the process have been known to adhere to an all capital letter expression of the word, i.e., SCRUM.

Ger defined two roles that fit in two distinct groups–pigs and chickens–based on the nature of their involvement in the development process. These groups get their names from a joke about a pig and a chicken opening a restaurant:

A pig and a chicken are walking down a road. The chicken looks at the pig and says, “Hey, why don’t we open a restaurant?” The pig looks back at the chicken and says, “Good idea, what do you want to call it?” The chicken thinks about it and says, “Why don’t we call it ‘Ham and Eggs’?” “I don’t think so,” says the pig, “I’d be committed, but you’d only be involved.”

“Pig” roles

The Pigs are the ones committed to the project in the Scrum process – they are the ones with “their bacon on the line.”

“Chicken” roles

Chicken roles are not part of the actual Scrum process, but must be taken into account. They are people for whom the software is being built.

—-

Work is divided into Sprints -

A time period (typically 2–4 weeks) in which development occurs on a set of backlog items that the Team has committed to.

Scrum works on effective meetings. Meeting are categorised as follows:

Daily Scrum
Each day during the sprint, a project status meeting occurs.
  • The meeting starts precisely on time.  Often there are team-decided punishments for tardiness (e.g. money, push-ups, hanging a rubber chicken around your neck)
  • All are welcome, but only “pigs” may speak
  • The meeting is time limited to 15 minutes
  • The meeting should happen at the same location and same time every day
During the meeting, each team member answers three questions:

  • What have you done since yesterday?
  • What are you planning to do today?
  • Do you have any road blocks preventing you from achieving the todays task?
Scrum of scrums
Each day normally after the daily scrum.

  • These meetings allow clusters of teams to discuss their work, focusing especially on areas of overlap and integration.
  • A designated person from each team attends.

Because you are startup the scrum of scrums will only become part of your routine when you have teams of works.. for the moment the daily scrum seems enough for us. We organise further meetings/calls when we need it.

Sprint Planning Meeting
At the beginning of the sprint cycle (every 15–30 days), a “Sprint Planning Meeting” is held.

  • Select what work is to be done
  • Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team
  • Identify and communicate how much of the work is likely to be done during the current sprint
  • Eight hour limit

800px-Scrum_process

How do you present a Sprint ?

Simple .. Piece of Paper and Yellow Sticky notes..

Have a column for

  • To do
  • In Process
  • Done

Assign the work to each of the team players and review the board on the daily meeting.

scrumban-001

Have a little fun and the work won’t seem so bad..

  1. Ah taking lessons in common sense I see!

    Interesting the way they call it a “scrumban”, looks like you’re also leaning (pun intended) towards kanban! ;o)

    The biggest danger I see with people getting excited about Scrum/Lean/Agile etc is that the core concept can be forgotten in an effort to follow a process or desire to be “Agile”.

    The key to good project management is change management and the willingness to tailor these guides to fit your own style and ways of working – once you start enforcing Scrum practices you end up with a process and a static process brings with it all the failings of every other software engineering methodology out there.

    There’s a nice saying from the Lean community which captures the most important thing about your poject… *success*

    In Kanban/Lean we focus on being successful and thus hopefully get to be agile. In Scrum/Agile we focus on being agile and thus hopefully get to be successful.

  2. O, I agree – you need to be flexible. Being a startup, you have the ability to react quickly and respond without going through a huge chain of command!

    the thing is and point of the post is that you need some sort of Project management.. otherwise it’s bound to fail! The concept or framework of scrum suits us @ Cauwill – so we use it. In fact we were kinda always doing it – but didn’t know it was called SCRUM!

    R

Trackbacks/Pingbacks

  1. coclarity » Project Management LEAP programme - [...] and day of training on project management. One of the LEAP participants, Ronan Skehill wrote a great summary of ...

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>