IT Governance are now selling my book, the Concise PRINCE2, which is a little ‘crammer’ for two groups of people (a) those intending to take the Foundation exam (b) those project managers who would like the comfort of a pocketbook that gave them all the key words, themes and processes, without having to lug the manual around or go chasing off to reference it. It really does fit in a pocket or handbag, and at £9.99 it won’t make a hole in your pocket.
Translations of The Essence of PRINCE2 are now available in Slovak-English and Czech-English. Contact Branislav Gablas at firstname.lastname@example.org or use one of these links
I have been debating with myself on whether to create more sample Practitioner papers. It seems that the APMG website has gone down to just one sample, although I thought that we had two. Another thought – the new style Practitioner exams are easy to be marked by computer, ensuring a rapid turn-round, but do they show the same level of in-depth knowledge of the method that the old essay-style papers used to do, e.g. the creation of a product-based PBS and PFD?
I am in the process of re-reading and updating my book, “The Essence of PRINCE2” and “The Art of PRINCE2 Survival”, not only to keep me thinking, but I think that it’s time that I looked afresh behind the words that describe the method. I’m not convinced that all of the authors of the 2009 version were fully ‘au fait’ with every part of the method that was rewritten, and some of it is not that easy to simply implement. I’ve also never had feedback on my suggested simplified Issue/Risk Register. For me it worked well. Any experiences out there?
Tagged with: risk register
Posted in Blog
Just had a nice quote from someone who bought this book:
“What a brilliant book. Concise, relevant and straightforward. I have over the years used bits and pieces of what you have presented, but nothing as crisp as your Benefits of PRINCE2 approach.”
I have a new book on the market, PRINCE2 Rollout Approach. In it I suggest a way of approaching all those live projects that are not currently using PRINCE2. Why let them run on without the PRINCE2 control and structure? Will they give you warnings of problems that might affect quality, budget or delivery date? The book offers a staged, painless way to add just those PRINCE2 features that will bring benefit to these projects; no overkill, no huge upheaval. If you know of a company that is implementing PRINCE2, help yourself to this practical advice.