Please login or join to subscribe to this thread
please refer to the following discussion threads for your input:
MP4PM: Statement of work - opportunity/business need/Goals/Scope
MP4PM: Statement of work - Scheduling Goals / Key Milestones
MP4PM: Statement of work - Success Cirteria/ cost estimates
MP4PM: Statement of work - Assumptions / Constraints / Requirements
If you have any additional topcis that you do miss actually please do not hesitate to post them here.
Thanks for your inputs in advance.
could you please check the link to the map? I just get a blank page but no error message.
Thank you for this post and series. It is especially helpful as a project manager to be spending this extra time delving into the details of items that we "get used to" making day in and day out. You articles that you posted have been extremely helpful and I look forward to reading more of your posts.
just checked the link and it works for me. I do use the FF Brwoser latest version.
Sometimes the map needs a bit of time to be loaded.
May be you have some add blocker or noscript active?
Anyone else with that experience?
Thilo, if it still doesn't work for you please send me your email via pm and i will send you the map directly.
very nice to see a new face participating in the discussion, highly appreciated!
And many thanks for your kind words, such feedback is really encouraging and motivating.
today the link worked, no changes were necessary from my side. The map indeed takes some time to load. I probably just had a very slow connection yesterday and maybe not enough patience...
Merry Christmas and a Happy New Year! Have some happy and restful holidays.
took me a while to find the time to go through the map. So here are my comments:
- the point of restrictions in the assumptions branch and the branch constraints seem very similar, the only difference I see that might be relevant for a project manager is that there could be things that the project is not allowed to touch, even if that means objectives will not be achieved while others may be fair game to change/influence if need be; this differences should be clarified with the Sponsor and/or steering committee
- it might help the user to have a glossary and once you've established it go through the map and use it to make the wording uniform
- again there is some overlap with the other maps, which of course is only natural; in the same vein as the comments above, maybe at the end of this effort it makes sense to go through everything and look if maybe some elements of a map would also fit into others
still a happy new year to you. ;)
No worries, i know that we all have a lot to do (there are some projects to be managed for sure, i guess;) ). I am glad for any inputs.
regarding the restrictions/constraints branches:
i saw your point and have tweeked this now a bit, i have moved the restrictions branch up to the constraints section and named it "other restrictions" in addition to the already existing constraint branches. I guess this way around it makes more sense.
Thank you for that, update will come soon.
I am not sure if i got the point regarding the glossary in the right way ... do you think we should rely on the PMI glossary? To define an additional glossary seems not much useful to me ... or did i got you totally wrong here?
Regarding the overlaps:
Like you said it, this is just natural within this initiative sice we want to align as close to the PMBoK Guide as we can.
For instance: the SOW will not be used in any project. External projects mostly have somewhat contract/business case/other business documents and a SOW will not be needed there. Internal projects often do miss something like contractual documents and a SOW might be more appropriate here.
And of course in some projects you will have both ...
In the end it is a matter of tayloring the MP4PM framework (not to say the PMBoK Guide processes) to the specific project needs.
And the good news is that it is very easy to transfer information already recorded in one map to another where it is also needed, right?
But of course we will try to align all the maps in a way to avoid unnecessary efforts (this will be an ongoing task i guess ...;) ).
Like always Thilo, many thanks for your valuable inputs, highly apprciated!
Hope to see you in the webinar ...;)
I hope you had a great start into 2017. Regarding the glossary I'd indeed recommend to stick to the PMI/PMBoK definitions, but moreover, I think that there are some terms (take the example of constraints and restrictions for example) where it would be helpful to establish a glossary so that in all maps you would not use different words for the same thing. I do not think that the user would need a glossary to get definitions on the terms, but like me they might wonder about nuances/subtleties in the word's meaning that just are not there.
Regarding the overlaps, the maps will make it easy to customize things, you just have to know about this option. Users new to project management might not know about all the overlaps and experienced PMs who are new to mind maps might also miss the opportunity because they do not know about the advantages of mind maps. It is just a thing of being aware what you can do with this tool.
totally forgot: Of course, I really would like to attend the webinar. Do you already have an idea regarding the date?
Please login or join to reply