Can you do away with the Project Initiation Meeting?

Project initiation meetings are often skipped to fast-track projects. Once a sponsor is found, organisations go straight to project planning and execution. But based on our own experience, holding a project initiation meeting can actually eliminate many issues that may crop up in the future and hence may speed things up instead in the long run.

It is in the project initiation meeting where your project objectives and scope are clarified and all stakeholders are brought to the same page. Project sponsors and stakeholders will have to know in a nutshell what is needed from them, what the possible risks are, what different resources are required, and so on. So that, when it’s time to proceed to the next phase, everyone is already in-sync.

So what are taken up in such a meeting? Perhaps an actual example can help. Sometime in the past, we set out to work on an eCommerce website project. After conducting the project initiation meeting, these were some of the things we were able to accomplish:

  • Identified deliverables e.g. site design, interface to payment system, etc.
  • Come up with the project phases
  • Agreed what should be in and out of scope
  • Defined the acceptance test criteria
  • Identified possible risks
  • Identified the possible training and documentation work needed
  • Established whether any analysis was required, e.g. as with regards to payment interfaces
  • Formulated disaster recovery plans
  • Defined roles and responsibilities
  • Drafted timelines and due dates

Aren’t these covered in project planning? If the project is a big one, the answer is no. In a large project, project planning is a much more exhaustive activity. In a project initiation meeting, only the basic framework is defined.

Some questions may still remain unanswered after a project initiation meeting, but at least you already know what answers you need to look for. In the example we gave earlier, we left the meeting knowing that we needed:

  • a list of all necessary hardware to estimate the costs
  • to identify possible dependencies we might have with third parties
  • to identify what software had to be bought and what skills we needed to hire

When it was time to proceed to project planning, everyone involved already knew what direction we were taking. In effect, by not skipping the project initiation meeting, we were able to avoid many potential obstacles.

Check our similar posts

Cloud Computing Trends: Where is the Cloud Headed Next?

Cloud adoption has been quick and painless at the consumer level. For instance, everyone’s on Gmail, YouTube, Facebook and Twitter on a daily basis yet most think nothing of the fact that they’re already using cloud-based services. Small businesses have also discovered how cloud solutions have raised efficiency in the workplace up a notch or two, while also bringing about significant cost savings. Cloud applications, particularly those for communication, file sharing, office software, backup and storage, and customer management, have rapidly grown in usage among SMBs.

In the same manner, large corporations are starting to see the potential of moving some of their IT department, whether its infrastructure or network management, to the cloud. By all indications it would seem that whether we are ready for it or not, cloud computing technology is here for the long haul.

So where is the cloud headed to next? In this post we examine the trends in the world of cloud computing and what likely lies in store in the near future for cloud users.

Focus on Security

Security has always been a key concern in the cloud computing industry and this will not go away anytime soon. If anything, data security in the cloud will only get to be in the limelight even more as cloud adopters grow in number. That’s why we expect professional cloud services providers to start implementing measures that will help slowly build up confidence in cloud security.

We should soon see more advanced security techniques and protocols that would increase the overall level of privacy and protection for cloud-stored information. Tighter security for login encryptions and prevention of unauthorized access are priority although there are a lot more issues that may need to be addressed. Now it remains to be seen whether these moves are enough for corporate clients to put their full trust in the cloud. But then again, they can always find ways to stay secure while making use of cloud computing where they can, which brings us to the next cloud trend.

Hybrid Approach

Large businesses are taking a longer time to get used to and actually use cloud services, and understandably so. After all, these companies have more at stake when it comes to dealing with such valid issues as security, compliance, outages, legacy systems, and more. However, they also cannot ignore the very appealing characteristics of the cloud. For big companies that have substantial IT needs, scalability, business agility, and faster deployment are listed as the biggest draws of the cloud.

This is why analysts predict that as as these businesses look toward leveraging the benefits of the cloud while at the same time maintaining control over mission critical data and systems, the use of a hybrid approach, i.e. putting some services in a public and at the same time opting to utilize a private cloud for other applications, will see enormous growth.

Mobile Cloud Computing

The BYOD or Bring Your Own Device business policy is another emerging trend that would not have been possible if not for cloud technology. This practice involves having employees bring their mobile devices to work, allowing them to access company files, data, and applications from their personally-owned gadgets in and out of the workplace.

As with any new business practice, the concept of BYOD can be both advantageous and disadvantageous. On the one hand, some believe it helps increase employee productivity and lifts their morale, while reducing overall IT costs. On the other hand, BYOD also opens up a whole new set of problems that are quite consistent with what many businesses take issue with with cloud technology: security. Do the pros outweigh the cons or vice versa? This much isn’t clear yet but what is evident is that more cloud apps are going mobile.

Efficiency, Innovation

While cost savings has always been one benefit that cloud proponents are quick to point out, its capability to improve and streamline business processes, thereby increasing efficiency and agility within the organization, is another key opportunity that the cloud offers. This is evident when you take a look at the most commonly used cloud services: backup and archiving, business continuity, collaboration tools, and big data processing.

Moreover, the cloud is making it easier for individuals to create new products and produce new lines of business. With access to higher IT capacity at lesser cost and at faster deployment rates, businesses can scale into more innovation without having to worry about the availability of computing resources.

Contact Us

  • (+353)(0)1-443-3807 – IRL
  • (+44)(0)20-7193-9751 – UK
Can you do away with the Project Initiation Meeting?

Project initiation meetings are often skipped to fast-track projects. Once a sponsor is found, organisations go straight to project planning and execution. But based on our own experience, holding a project initiation meeting can actually eliminate many issues that may crop up in the future and hence may speed things up instead in the long run.

It is in the project initiation meeting where your project objectives and scope are clarified and all stakeholders are brought to the same page. Project sponsors and stakeholders will have to know in a nutshell what is needed from them, what the possible risks are, what different resources are required, and so on. So that, when it’s time to proceed to the next phase, everyone is already in-sync.

So what are taken up in such a meeting? Perhaps an actual example can help. Sometime in the past, we set out to work on an eCommerce website project. After conducting the project initiation meeting, these were some of the things we were able to accomplish:

  • Identified deliverables e.g. site design, interface to payment system, etc.
  • Come up with the project phases
  • Agreed what should be in and out of scope
  • Defined the acceptance test criteria
  • Identified possible risks
  • Identified the possible training and documentation work needed
  • Established whether any analysis was required, e.g. as with regards to payment interfaces
  • Formulated disaster recovery plans
  • Defined roles and responsibilities
  • Drafted timelines and due dates

Aren’t these covered in project planning? If the project is a big one, the answer is no. In a large project, project planning is a much more exhaustive activity. In a project initiation meeting, only the basic framework is defined.

Some questions may still remain unanswered after a project initiation meeting, but at least you already know what answers you need to look for. In the example we gave earlier, we left the meeting knowing that we needed:

  • a list of all necessary hardware to estimate the costs
  • to identify possible dependencies we might have with third parties
  • to identify what software had to be bought and what skills we needed to hire

When it was time to proceed to project planning, everyone involved already knew what direction we were taking. In effect, by not skipping the project initiation meeting, we were able to avoid many potential obstacles.

Is Your Project Agile, a Scrum or a Kanban?

Few projects pan out the way we expect when starting out. This is normal in any creative planning phase. We half suspect the ones that follow a straight line are the exceptions to the rule. Urban legend has it; Edison made a thousand prototypes before his first bulb lit up, and then went on to comment, ?genius is 1% inspiration, 99% perspiration?. Later, he added that many of life’s failures are people who did not realise just how close they were to success when they gave up.

So be it to this day, and so be it with project planning too. There is no one size fits all approach when it comes to it. Agile, Scrum and Kanban each have their supporters and places where they do well. Project planning often works best when we use a sequential combination of them, appropriate to what is currently happening on the ground.

Of the three, Agile is by far the most comprehensive. It provides a structure that begins with project vision / conceptualisation, and goes as far as celebration when the job is over, and retrospective discussion afterwards. However, the emphasis on daily planning meetings may dent freethinking, and even smother it.

Scrum on the other hand says ?forget all that bureaucracy?. There is a job to do and today is the day we are going to do it. Although the core Agile teamwork is still there it ignores macro project planning, and could not be bothered with staying in touch with customers. If using Scrum, it is best to give those jobs to someone else.

The joker in the pack is Kanban, It believes that rules are there to substitute for thought, and that true progress only comes from responsible freedom. It belongs in mature organisations that have passed through Scrum and Agile phases and have embarked on a voyage towards perfection.

That said, there can be no substitute for human leadership, especially when defined as the social influence that binds the efforts of others towards a single task.

Ready to work with Denizon?