Skip to main content

Effective Project Management for Web Geeks [Work Smarter]

Popularity Report

Total Popularity Score: 0
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...

Rank

Bookmark History

Saved by 12 people (3 private), first by anonymouse user on 2007-06-19


Public Sticky notes

The second perception is that PM takes a huge amount of time. This can certainly be true: if you try to do everything that traditional PM demands it can definitely turn into a full-time job. There's a balancing act between the "science" of PM (what you're told you should do) and the "art" of project management (what you actually need to do).

Highlighted by dyhatchett

The first is the perception that PM distracts from the "real work," whether it be designing, coding, or some other facet of web work. The unfortunate reality, however, is that without appropriate PM the "real work" expended can all be for nothing -- what you build might be beautiful, but if it doesn't help if it's the wrong thing.

Highlighted by dyhatchett

So what's So Hard about That?

When you look at the project lifecycle this way, it all seems like common sense. So why do so many projects suffer from delays, overrun budgets, or fail to deliver the desired features and quality? The reality is that paying attention to the different phases of a project isn't hard and doesn't even require much time. Unfortunately, however, there are two perceptions that mean people seldom give PM the attention it needs.

Highlighted by dyhatchett

So, what IS Project Management?

Highlighted by dyhatchett

A less abstract version of this definition is that PM is what you need to make a project happen on time, within budget, with required scope, and quality.

My personal definition is that PM is the simplest way to look like a superhero without requiring the involvement of any radioactive spiders or questionable parentage.

Highlighted by dyhatchett

PM is all about making the project happen -- how you complete the work that you need to do for the project is up to you.

Highlighted by dyhatchett

The Generic Project Lifecycle

The generic project lifecycle is fairly simple -- first you begin the project (Initiation), then you go on to actually do the project (Planning, Executing, and Controlling, which form a loop, since expecting things to go right first time is rather unrealistic) and finally you finish by making everyone happy and, with any luck, receiving payment (Closure). This process is illustrated in Figure 1.

The project lifecycle (click to view image)

Figure 1. The project lifecycle (see larger image in new window)

Since typically most time and effort is spent in the Executing (completing tasks) and Controlling (keeping everything on track) phases, many people think these are the most important. It is true that these should be where you spend most of your time -- after all, nothing would be completed if you didn't! -- but they are not the most important.

The most important project phases are Initiation, Planning, and Closure.

Highlighted by dyhatchett

Typically, this last will mean putting in place some sort of support structure. If you're going to deal with the ongoing support and maintenance yourself, then you need a Service Level Agreement, as we'll see shortly. If you're handing over to another team, then you need to make sure they have the training and documentation that they need.

Highlighted by dyhatchett

Initiation

Highlighted by dyhatchett

I often argue that the most important project phase is that of initiation. It's where you make the contract (or agreement, if you are doing projects internal to an organization) with your clients, work out why the project is happening, what you're trying to achieve, and what defines the project's success.

Highlighted by dyhatchett

Projects that are set up correctly are much more likely to succeed than those that aren't. This means that making clear what the expectations and objectives are from the outset is important. It also means that defining what success looks like is essential. At this stage it's also useful to look at assumptions (for example, the company's branding might be expected to stay the same for the duration of the project) and the constraints (such as the people who need to approve the design might be away on holiday for the whole of September).

Highlighted by dyhatchett

Planning

Highlighted by dyhatchett

Planning is very important, but often not for the reasons that people assume. There are a few reasons to plan, including:

  • forming a better understanding of what needs to be achieved
  • identifying dependencies (such as the design needing to be completed before it can be coded)
  • communicating with the client
  • collaborating with your team members, so that everyone understands the big picture and the implications if delays are experienced

Highlighted by dyhatchett

Much as you may be able to plan tomorrow's work in detail, it's impossible to plan an entire project in lots of detail at the outset. It's also unnecessary: yes, you need to know the key milestones that need to be delivered, the dependencies, and rough timelines, but trying to plan down to the day, hour, or minute at the outset of the project is futile. Nothing stays the same for long enough for that approach to make sense.

Highlighted by dyhatchett

Also of great importance to the planning stage is identifying who is going to be involved with the project, both on your side (who's going to be in your team?) and on the client's side (who will you be dealing with and receiving input from?) The term stakeholder refers to anyone who has some interest in your project; this may include the marketing people who want to use the web site you're developing as a marketing tool, the admins who will be asked to add new content, and the salespeople who may want to make sure the web site doesn't say too much and that they still have plenty of negotiation room.

It's important when identifying stakeholders to remember that hierarchy doesn't define importance where your project is concerned -- if the admin team find it too hard to update, their lack of support can be just as damaging as when the CEO doesn't like the color scheme.

Highlighted by dyhatchett

Closure

Web projects don't end when the site goes live. If you've ever tried to just send a site live and then held out your hand for the check, you'll have experienced what I term the "undead stakeholder" phenomenon: people who had a stake in the project returning again and again with more requests or improvements or even just support queries. The reality is that your project isn't finished until the key stakeholders agree that it's finished, which is another reason why defining the success of the project in the initiation phase is so important.

Highlighted by dyhatchett

So what do you need to do in the closure phase? Firstly, you need to demonstrate that you have met the success criteria. Secondly, you need to obtain the stakeholders' agreement that you have met the success criteria. Thirdly, you need to make sure that the future of the product you developed (whether it be an application or a web site) is assured.

Highlighted by dyhatchett

Highlighted by dyhatchett

"Project Management" has always been a term more likely to elicit a groan than a smile. Nevertheless, the use of project management skills is often what distinguishes an easy, successful project from a painful and unsatisfactory one. In a world where clients and business partners increasingly want a full solution, rather than just the component pieces of design and code, having basic project management skills, at least, is quickly becoming a requirement for web professionals.

Highlighted by joel

The generic project lifecycle is fairly simple -- first you begin the project (Initiation), then you go on to actually do the project (Planning, Executing, and Controlling, which form a loop, since expecting things to go right first time is rather unrealistic) and finally you finish by making everyone happy and, with any luck, receiving payment (Closure). This process is illustrated in Figure 1.

The project lifecycle (click to view image)

Figure 1. The project lifecycle (see larger image in new window)

Highlighted by joel

You'll notice that I don't list "so you can follow it slavishly" as a reason for planning. Much as you may be able to plan tomorrow's work in detail, it's impossible to plan an entire project in lots of detail at the outset. It's also unnecessary: yes, you need to know the key milestones that need to be delivered, the dependencies, and rough timelines, but trying to plan down to the day, hour, or minute at the outset of the project is futile. Nothing stays the same for long enough for that approach to make sense.

Highlighted by joel