Essentials of Project Planning

Budgets and Start Ups

“Organizing is what you do before you do something, so that when you do it, it is not all mixed up” A A Milne. I love this quotation as it so clearly illustrates the importance of planning. Often the most neglected stage in most projects is the planning stage where the project is given its clear direction and a common understanding is created. Although when this stage is missed or played lip service to things will end being “all mixed up”.

Lets take a look at a outline of the planning process.

Google Wave

Google Wave snapshots inboxI have just been watching this and think that Goggle may have just unveiled the future of collaboration software. Although in its infancy and with concerns around security and other elements this should make dispersed team communication much easier and may spell the end of share-point as a corporate tool in it current form. (I can see Microsoft moving in this direction as well).

Agile Retrospective – Lessons Learned

MPj04034140000[1]The one phase that is most often neglected in agile development is the retrospective, fulfilling the same role as lessons learned in other methodologies such as Prince2. Only paying lip service to the retrospective will have noticeable effect on the delivery of the project it is in this phase that misunderstandings are outlined and process that have not went well are addressed.

Some Project Managers focus on this in a very structured way moving from one defined stage to the next, I have over time come to believe that a structure is important to focus the meeting but a strict agenda has never really achieved the best results.  What I want to outline are general principles that should be included in any retrospective, remembering that each section will naturally flow together and it is the PM job to bring them back to the necessary stage and maintain relevance and focus.

Lets look at what a retrospective should include:

Agile Development in a Commercial Organisation

Agile Development in a Commercial Organisation“100 grand spent on half finished software is worth nothing” This statement sums up the problem with conventional long cycle development, In the current commercial environment the ability to change focus and deliver value is more critical than ever. Agile development will allow a company to Having been an advocate of Agile development and project management for some years now it is good to a increase in the adoption of these methodology in the mainstream commercial arena. From working with clients over the last few years the main reasons for adoption is:

Communication in Web Projects


Is web project management that different from other forms of project management in theory no, but the difference is that the average web project manager has no background and training as a conventional PM,  they have come from a design and communication background.

And this might be the reason that their are so many good Project Managers working within web projects, why? they have come from a background based on communication and understanding relationships over a delivery methodology.

Web 2.0

Web 2.0 is the business revolution in the computer industry caused by the move to the Internet as platform, and an attempt to understand the rules for success on that new platform.”  Tim O’Reilly

Web 1.0 was the imitation of print media online and other than perhaps a basic search and possibly a facility to order there was no real ability for the user to interact with the site or other humans. This is still sadly in many cases still the norm, have a look at some of the successfully sites on the web right now.

It was the growth of the Web 1.0 site and ecommerce that gave birth to user experience and page analytics, the creators and innovators in these fields that changed business understanding of the potential and potential to build some form of meaningful customer interaction.