Category Archives: Project Management

8 Interview tips you need to know – PM Career Tips

So you’ve worked hard to get noticed by the employers or been through the battle of getting recruiters to represent you and the hard work has paid off as you have an interview pending, or if you are fortunate then you may have a few lined up. This is the point where you don’t sit back and wait for the day; you need to apply yourself to really impress the interviewers. Often those who have reworked their CVs find it an important refresher for what they have done over the years and it really brings home the fact that we easily forget important (and relevant to interviews) pieces of work. Also those who have sat comfortably in a role for a long time or have secured assignments without interviews will not be as prepared as those who regularly go for interview. Here’s a guide to getting yourself ready and creating a good impression at interview:

 

  1. Go through your CV and refresh yourself on what you have been doing over the past few years, pay particular attention to areas relevant to the role you are interviewing for and dig deep into your memories by walking through assignments step by step to draw out any additional detail which may not be addressed on the CV.
  2. Read the job description and draw out key areas of requirement, those listed core competencies are a good starting point. For example if they are asking for Change Management then you will need to supply a good example of when you have managed change, think about the bereavement curve, what the key challenges were and how you overcame them.
  3. Start to pull out some strong examples which you feel will be good to talk about and apply the STAR technique (Situation, Task, Actions, Results), be clear on the message you want to deliver and keep to the facts, being theoretical is not useful to the interviewer especially when you’ve actually done it so tell them how it was.Interview Preparation
  4. Examples of work, some interviewers may ask you to take an example of a stakeholder communication plan or project plan – in this case take a portfolio with some strong examples and be prepared to answer questions about it.
  5. Research the company, so many people barely do this so take time to really understand what the business does and what key challenges they may be facing, who are their competitors, what’s new on their news pages. Also take a look about what others are saying about them, know all there is to know – really demonstrate your buy-in to them and the role.
  6. Do a dummy run to the offices – don’t leave the journey to chance. It is always good practice to time how long it takes and which trains/buses you need to take (or where to park the car) and going at the same time of day as the interview will take place a day or two before will give you a good idea of traffic etc. Do remember to take enough change for the meter if you are driving, I have known one candidate turn up to interview stating they can only stay for half an hour as they only had enough change for that on the meter – yes really!
  7. Organise what you are going to wear a day or two before; ideally all should wear a suit or smart office clothes, even those who are fashion conscious need to tone it down for an interview. Nothing too outlandish or uncomfortable either.
  8. Put together some good questions to ask the interviewer, it is good practice to think through the role and business – this will naturally bring up some questions about how you will fit into the team, what you’ll be doing and what is expected from you within the first few weeks/months. Write a list, better to include more than you’ll ask as some will inevitably be covered by the interviewer during discussion.

Doing Agile Project Management With Scrum

“What does the game of rugby and modern management techniques have in common?” one may ask! If you are into ‘Agile Project Management’ and use ‘Scrum,’ you already know the answer. It is interesting to see, how rugby has inspired one of the most time-effective and cost-efficient management techniques of the day. Agile Project Management, is a specialized area of project management. Here, the resources and budgets are fixed variables; however, it is a more open ended approach compared to regular project management. It enables managers to optimally utilize resources and create products and services, which meet customer requirements, more satisfactorily and profitably.

A Brief History

First conceptualized in 1986, by Hirotaka Takeuchi and Ikujiro Nonaka, Agile Project Management, is based on the approach rugby players’ use. Just like rugby players constantly assess and reassess situations, altering their strategies and responses at different points of time during a game, to score against the opponent team; likewise, managers through this highly collaborative method – use repetitive deliveries and customer feedback at different stages of a project, to reassess and rework on ‘a product or service being developed.’ The process is repeated until the product is improved, refined and becomes completely market ready.

‘Scrum,’ a software development framework, is used in Agile Project Management, to manage projects where software related products or applications are being designed. It allows the formation of self-organizing teams by enabling co-location of all team members, and promotes verbal communication across team members and disciplines in a project. The term ‘Scrum’ again owes its origin to the game of rugby, in which, it is the shorter version of the word –‘scrummage;’ and refers to the manner of restarting play in rugby football. It is popular especially in the IT industry, where the nature of projects or ‘products being developed’ – is comparatively newer, more innovative and highly complex. Since these are too difficult to comprehend before being tested out, they are allowed to evolve gradually.

Scrum Terminologies

There exists in Agile Project Management, an interdependence of a sequence of activities, where one set of activities is affected by the other. The final product is the outcome of a series of repetitive deliveries with short deadlines. Delivery cycles are referred to in ‘Scrum’ lingo, as ‘sprints’ and each ‘sprint’ varies from a week to a month, though usually a fortnight is its normal duration. “…reviewing each sprint before moving to the next means that testing is conducted throughout the process, which allows teams to change the scope or direction of the project at any point,” states Daria Kelly Uhlig, emphasizing on the advantage of using this technique.

Peculiar as it sounds, the different levels of project stakeholders in Agile Project Management using Scrum, are referred to as –‘pigs’ and ‘chickens!’ Here ‘pigs’ represent the ‘Scrum team’ who perform core functions like producing the product. The Scrum team generally has a Product Owner, a Development team and a Scrum Master. On the other hand ‘chickens’ represent the ‘Supplementary team,’ whose roles are not that important but are never the less, necessary.

The usage of both these terms is derived from ‘The Chicken and the Pig’ fable, in which different levels of commitment are shown, through the examples of a pig and a chicken. “When producing a dish made of ham and eggs, the pig provides the ham which requires his sacrifice and the chicken provides the eggs which are not difficult to produce. Thus the pig is really committed in that dish while the chicken is only involved, yet both are needed to produce the dish,” the Wikipedia page on the story, notes.

Agile Project Management with Scrum, is a more flexible approach to project management. It uses open, instant and regular communication and focuses on greater team involvement and client participation. Here, having a knack for problem solving, negotiation and communication is necessary and precedence is given to common sense over written policy. “Scrum is designed to optimize team satisfaction and productivity, product quality, responsiveness to customers, and transparency for stakeholders. The key practices that enable these benefits include de-emphasizing work on non-deliverable items, implementing and finishing each Story in a Sprint Backlog in rank order, working in short Sprints of 2-4 weeks, and making past, present, and future project information available to all stakeholders,” concludes Kevin Thompson on cPrime.com.  

Featured images:

This article was written by Hugh Swift a management expert and corporate trainer, who conducts workshops on Agile Project Management.

Does your PM CV meet your salary requirements? PM CV Tips

All too often I am approached by PPM professionals asking me why they are not getting into shortlists for roles commensurate to their salary/day rates and experience. One look through the CV will tell me all I need to know about why the applications are not being taken seriously, if the CV is well balanced with project detail and core competencies then it is usually that the CV doesn’t speak the right level of seniority and responsibility.  Overlooked have been key areas such as team management (and direct line management which is less common with PPM professionals these days thanks to matrix environments), levels of management dealt with and of course complexity of projects (with the issues that these attract). Do not assume a job title will cover core areas of responsibility as titles can be very deceptive from organisation to organisation. If you are working at programme level then one would expect to see some reference to the elements of programme management required in order to carry out your role, project support professionals need to address the core areas they are covering such as interfacing the PM teams with senior management as standard and look into areas such as building project capability. Are you hands on or do you orchestrate teams? Or a bit of both, talk to us about how you deliver and deal with underperforming staff. Training and mentoring individuals and teams tends to be par for the course with most PPM professionals however not all and there are many ways to administer and gain buy-in; from your teams and also from your senior stakeholders.

Money

There may be elements of change management you apply to your delivery and particular emphasis on risk – talk about these, all core areas sought after by employers. Don’t get caught into repetition on the CV – you may deliver similarly from role to role but there are always subtle differences, make sure you draw these out to add more value to the CV rather than stating “same responsibilities as XYZ role”. Cover as many elements of the project lifecycle as possible running through the roles so you can really start to tick the boxes of the hiring manager’s wish list. As a contractor you may have some fantastic war stories you can share – talking through how you hit the ground running and trouble shoot, and don’t forget that all important handover to BAU. Employers would much rather have a contractor come in and solve their issues and leave the team capable of continuing the good work once you leave. Always adding value, thinking about the end goal and how you can be attractive to your next employer is very important – don’t sell yourself short.

Contracting – PM CV Tips

Performing the role of an interim Project Management professional is rather different to an employee position – obvious differences are that you are a temporary resource and as such you are paid (usually a good rate) to go in and address core business needs, and provide a robust solution.

Often you will face resistance by permanent staff and are viewed as the bad guy as opposed to the solution provider, it is not a role for the feint hearted and as such you will develop a style (and thick skin) which is flexible and understand the need to bring teams on board quickly without giving the impression you are stepping on toes but still meet overarching business goals.

Here’s a list of some things which you should consider if looking to take the plunge into contracting:

  • No inductions – unlike the employee route which will have you sat in week long inductions, the contractor will be thrown into the IT team to get set up on their systems and then you are on the start line (the starter pistol having been triggered weeks earlier).
  • Little support – as you are likely to be commanding a high day rate you will be deemed an expert in your field, so don’t expect any hand holding, be ready to roll your sleeves up from the off.
  • No training – not true with every organisation, I have seen some businesses investing in training and qualifications for contractors, however this is a rarity and not something you should be expecting.
  • Expected to hit the ground running – As per the inductions bullet point, jumping straight in is the norm. You will develop a style over time where you will have a communications plan set up from the off, getting to know the teams and understanding their perspective is important.
  • Inheriting teams – although not always the case, some are lucky to be able to recruit their own team, whether internally or bringing in talent. But you will always come across assignments where the team has already been picked, not always ideal but a good leader will ascertain the teams’ abilities and needs quickly and ensure they are driving results.
  • Resistance – how many have tried before you, I have spoken to many a contractor who has taken an assignment which has previously had several PMs try and fail. In this instance you are likely to be met with teams who are waiting for you to fail or are just fed up with a newbie coming in and implementing yet another method of approach.

Contractor

Contractors by nature tend to get bored in their roles after a while which is why they choose to take this route, always looking for their next challenge and keen to be involved in problem solving. The best contractors really have the people element of PM nailed down, the ability to really understand people and lead from the front is key to being successful – arguably a skill which cannot necessarily be learned but can certainly be honed.