Keanu Reeves is a Better Career Advisor than Britney Spears

Guess who’s been writing internal news articles again? Below was produced to promote the tool I’m developing as part of a team for a sub-project at work. More details below but so far the reception to both writing and project outputs have been great.

 

Keanu Reeves is a Better Career Advisor than Britney Spears

 

When I was a little girl I wanted to be Britney Spears. Then around the age of seven I realised it would be a difficult career path (turns out it’s a ‘dead man’s shoes’ role), so instead I settled on hard-hitting journalism, only to find myself documenting the adventures of a pineapple in a party hat (don’t ask). Post University there were three years in charity and now I’m fast approaching two of the same at Nationwide but it’s only recently that the words ‘Project’ and ‘Management’ have sprung out as possibilities for someone like me.

I applied to be on a team for this year’s Association for Project Management (APM) challenge with echoes of Britney in the back of my mind. What skills and qualities do you

the-matrix-red-pill-blue-pill.jpg
Take on a crazy challenge alongside the day job or delete the email?

need to have to enter it? Where do you go to access accredited material? Is Project management even the right career? I was about to call it out on when someone else said it, and then another, until we’d all agreed that between our collective 17 and a half years’ experience no one knew the answers to these fundamental questions. Our deliverable was born; in four months we’d build a tool to help practitioners focus their development time more effectively. We would call it the “Project Development Matrix” (and Michael, our project manager, would tell me to stop suggesting we wear long coats and shades like Keanu Reeves’ did in the 1999 film The Matrix). With our tool all you’d need to do is answer a few questions and the answers would automatically populate charts to help tailor the development plan of the user.

 

The APM challenge is designed to develop project management qualities and knowledge of the project lifecycle. We produce detailed reports to deadlines, stage project boards with our sponsor and must deliver what we set out to do. For the finals night in May we’ll either have produce additional material or present to a panel. You’re up against teams from a range of organisations so company lingo has to be stripped away and everything taken back to APM fundamentals. The project would be enough of a challenge for a single co-located team, however we’ve added a layer of fun to the mix by basing ourselves across two Swindon and one London office.

Snow
Snow put central London into a state of paralysis

So where are we now? In February we housed a focus group to get consumer views and refine our ‘product backlog’ for the first release, with a view to develop and expand the tool and its use case after that. No project is entirely smooth running, given the snow I experienced in central London I struggled to see why the original focus group in Swindon had to be moved, but it’s the setbacks you learn best from.

 

The tool is presently due for release at the end of this month. Give it a go and let us know your thoughts. Any issues and I’ll don my shades and get Keanu to enter the Matrix himself and investigate further.

Waterfall vs Agile Project Management Models

Waterfall Project Management

When you complete each stage of a project in isolation. You can’t move onto the next stage until the previous one has been completed.

Teams may have frequent meetings in the form of monthly boards, where decisions are made by stakeholders, or dial in meetings with team members who may not work in the same office location (e.g. a Tester who works offshore).

waterfall-project-management.jpg
Waterfall Methodology

A project example would be upgrades to multiple interlinked computer servers. Server one must first be upgraded first before server two can be looked at.

Pros

  • Methodical and the traditional method of running projects.
  • Works well for projects where there’s one end goal and nothing in between.
  • Enables clear investment decision points and reviews at stage ends and also ensures everything is completed before progressing to the next stage.
  • (Pro or con!) results in stricter levels of governance as projects need to fulfil specific criteria before being allowed to develop and implement.

Cons

  • Slow. A hold up at one stage affects the rest of the chain for the project.
  • This also includes potential impacts on dependant projects who rely on other projects for meeting their deadlines.
  • This in turn can lead to resource inefficiencies, project overspend and failure to meet to time scales.

 

SELRES_18becb00-8b2c-49eb-bb78-305b4e1cf3bdSELRES_a42bbdd4-aaaf-44c1-801a-95ab1f7d3246SELRES_a92ed792-ef54-4bda-9325-efc9bfdaab93AgileSELRES_a92ed792-ef54-4bda-9325-efc9bfdaab93SELRES_a42bbdd4-aaaf-44c1-801a-95ab1f7d3246SELRES_18becb00-8b2c-49eb-bb78-305b4e1cf3bd Project Management

Instead of aiming to complete whole stages in isolation, Agile projects take a more cyclonic approach, tackling a project delivery in multiple smaller stages (or sprints). Sprints tend to last between two and four weeks.

Teams keep each other informed via stand up Kanban/scrum meetings. An appointed scrum master leads discussions to enable the different teams working on the project provide updates. A) with what they are going to tackle during each sprint (at the start), B) progress updates (during) and C) what they have achieved (at the end). Meetings tend to be more informal and visual compared to Waterfall and the use of whiteboards with post its and/or dedicated software are adopted more frequently to enable updates in a quicker paced project.

Agile-Development-diagram_03.png
Agile Project Methodology

An example of an Agile project would be the development of a App. Over the course of multiple sprints teams are able to gradually build and test the App, first with the basic code, then the functionality, then finally adding in user appeal – pictures, sounds etc.

Pros

  • Fast moving. Enables teams to quickly identify any faults and either fix or ‘drop’ them before too much money and time is invested.
  • Deliveries grow over time, a project leader can start to see formation much earlier into a project, where in Waterfall the change is sudden.
  • Considered to be a more resource efficient model and allows for greater collaboration.

Cons

  • Agile is not a suitable method for all projects. A single delivery can’t be built over time (for example, the delivery outcome ‘running a marathon’ cannot be done in separate sprints. You sign up, train, then run it. An Agile approach would be useless in this instance – you cannot gradually run bits of the marathon over twelve weeks!)
  • The working environment must contain all persons on the project (project lead, governance, software architects, testers, accountants, etc.) to enable collaboration. These resources can only be dedicated to one project or sprint. If resources are split between multiple projects (as they can be on Waterfall) then the sprint may fail to meet its delivery.
  • As sprints are quite short and projects adopting Agile are quicker paced, the project lead must ensure that suitable investment and project governance/review points are put in place as the cycle system doesn’t naturally allow for any sudden or prolonged stops.
  • As it’s a new methodology of project working, team members may require additional support and/or training.

 

 

And there you have it. A (very) quick overview of the two main methods of running projects. I want to add here that I am by no means an expert on either approach, having only started a career in business project management and governance three months ago(!) but hopefully for that reason it will help any new starters in the world get to grips with the basics.

(Also, I hope that doing this will stop Mumma Bennett getting into hysterics when I talk about my job- ‘Waterfall? Ha, ha, haah! What’s Waterfall?! I don’t understand, what’s water got to do with technology upgrades? You’re so corporate!’ and so on and so forth…)

 

And who says you don’t learn awesome things from this blog?