Find out that it really means to be a PM and get some top tips how to get the best from your team using PRINCE2 Agile method. At SPOCE, we compare the two.

1. ‘The Apprentice’Project Manager - some top tips for Lord Sugars PMs
By Richard Lampitt and Julia Gosse
Calling Lord Sugars PMs! Want to show Lord Sugar what you are really made of and how great a PM you really are?
Then you need to be prepared...Let PRINCE2 Agile® show you ther way and win that coveted prize.
As any fan of The Apprentice will know, it’s often the case
that when the role of Project Manager is up for grabs,
many of the wannabe protégés either suddenly become
very quiet, or they very keenly put themselves forward…
perhaps in part due to naivety!
Now, I know some may think the show a little far
detached from what actually goes on in real-life, and
people may think Lord Sugars version of the ‘Project
Manager’ role might well be as well...But is it? This
situation does highlight how leading a team involves a
certain amount of responsibility and interpersonal skills,
as well as ‘putting your neck on the line’! Are you up to
it? Read on and see.
The boardroom showdown!
While mishaps along the way might not mean the
equivalent of a ‘fast track to a boardroom showdown’,
project management can be quite stressful because
when projects are delayed, or over-budget – or even
fail – then it’s usually the Project Manager who is held
to account…. “You’re fired” springs to mind….rightly or
wrongly!
The comparison
Okay, we thought we’d throw out some comparisons
for you to read. In the following examples there are
somewhat negative and potentially stressful situations,
but then any Project Manager would know that such
situations usually come with the territory in the case
of poorly managed projects! However, delivering a
well-managed project on time to the agreed budget;
producing a deliverable to a business that meets
the expectations of that business; making sure the
deliverable is fit for purpose and capable of generating
the expected benefits...can be all very fulfilling and
motivating.
Take a look at the following examples and see for
yourself....
TRAINING PROFESSIONALS

2. Situation The Apprentice Response PRINCE2 Agile
The team are at logger heads and
two or more in the group can’t
agree on what would make their
solution acceptable.
A naive Project Manager
arrogantly goes for what they
think is the best solution,
because they are the Project
Manager after all and are
obviously in charge! Never mind
what the outcome is, or what it
looks like, just get
‘something’ created!
The Project Manager is
responsible for creating an
environment where the team are
empowered and responsible for
what they produce. A Product
Owner or Customer Subject
Matter Expert would be part of
the development team,
representing the business, and
they would be empowered to
make decisions on the suitability
of the solution.
The Team Manager would be
responsible for working with the
team to address any differences
of opinion. A facilitated workshop
could be held with a neutral
facilitator to help the team
resolve their differences.
No one knows what they are
meant to be doing and why, or
who they should liaise with
regarding what.
They all have very different and
conflicting ideas and are very
much in competition with each
other rather than working
collaboratively as a team.
They simply aimlessly get on with
the work which they believe the
Project Manager has instructed
them to do and then collectively
blame the Project Manager when
it proves to be wrong and the
outcome is unacceptable!
At the beginning of a work
package the Project Manager
should ensure that the team
agree the scope and objectives of
the task and the desired outcome
and the escalation path for issues
and risks.
The whole philosophy of working
in an Agile way depends on the
team working in a collaborative
way with high levels of trust and
transparency. The team
monitor this as part of their
ongoing introspection and work
together to address them. This is
based on the required behaviours
of transparency, collaboration,
rich communication,
self-organisation and exploration.

3. The Project Manager can’t get a
team member to willingly
undertake a task which has been
assigned to them. They are
demoralised and frustrated by the
lack of guidance being given to
them.
They argue, ignore each other
and then do a bit of back-
stabbing. The task may end out
getting completed but often
deliberately badly and/or
wrongly!
The key requirements are set and
prioritised at the beginning of the
relevant time-frame and the team
decides between them who is the
most appropriate person to do
the work.
The product may need to go
through a couple of iterations so
that a correct solution can evolve.
A safe to fail environment needs
to be fostered. It is recognised
that it is rare for a perfect
solution to be built without the
need for revisions.
If the situation still can’t be
resolved, raise an issue and
escalate to the appropriate
project board member to resolve,
e.g. if user related then Senior
User, if supplier related then to
Senior Supplier.
The Project Manager is constantly
interrupting the team for progress
reports
The team get frustrated by the
interruptions, breaking their
concentration and feel that they
are not trusted to get on with
their tasks.
The Project Manager can attend
the daily stand-up, as an observer
not a participant, to get a feel for
how things are progressing and
to pick up any issues that need
escalating.
Progress can be shown on an
information radiator and or burn
chart. This means that progress
information can be pulled by the
Project Manager when required.
Having a string of successful projects as well as industry accepted and internationally recognised
associated qualifications on a CV can be a significant career booster. Having a PRINCE2 qualification is
great but organisations are increasingly looking to agile ways of delivery to increase the speed of delivery
and business fit for their products. Blending PRINCE2 and agile gives the best of both worlds, structure
and agility to project delivery.
PRINCE2 Agile® is a registered trademarks of AXELOS Limited. PRINCE2 Agile Accredited Training Organisation logo is a trademark of AXELOS Limited.The
Swirl Logo™ is a trademark of AXELOS Limited. All trademarks are used under the permission, and remain the property, of their respective owners and are used for
identification purposes only.
SPOCE Project Management are proud to be trainers of the new PRINCE2 Agile qualification. If you
have any questions of you’d like to talk through anything regarding this innovative qualification then
why not get in touch?
Call 0800 177 7623
Email: clients@spoce.com
Visit: www.spoce.com