STEP 1: PRE-PLANNING: Get to know the tool you've just purchased and the resources available to you and your organization. Research IT! For tips on learning ServiceNOW and/or resources available. Review my post "5 Steps To Learning ServiceNOW, NOW!" Use IT! Most customers who've purchased ServiceNow will have at least a PROD and DEV instance available for there organization. If you'd like to stay away from using your DEV instance for playtime; then my recommendations would be to either navigate to the ServiceNow DEMO site or ServiceNow Developer site. Populate IT! Get your stakeholders on-board and in the tool. STEP 2: PLAN Make Sure Everyone Understands and Agrees on Strategy. Identify, Examine, and Correct Process Gaps (Where You Can) Before you start a "project" to implement ServiceNow take a few..
A Well thought out and written article.
*Common definition for SMART: Specific, Measurable, Actionable, Reasonable and Timed How often are your projects SMART? If you asked for that as a requirement, what are your expectations for a response?
In my opinion, requirements are the most under-rated aspect of most projects. In an unbelievable number of corporate projects they are completely non-existent and in the vast majority they are really no more than a paragraph or two of high-level requests which are unlikely to be delivered on successfully. In a very few of the countless projects I have worked on I have seen adequate, or an attempt at adequate, requirements. These projects, without fail, are the most successful projects that I have seen.
Why the passion, you ask? Without clear, complete and agreed upon requirements there is almost zero-chance, yes zero, that the project will be delivered successfully. And when I say successfully, I mean on-time, on-budget and matching the desired scope. Sure, most projects will get delivered without good requirements but you will see project delays (possibly numerous), budget overruns, and final scope that doesn’t satisfy the customer…
View original post 1,658 more words
Are you a PM, Consultant, or anyone involved with IT or Organizational projects? Then take some time to read this article.
If after reading you are interested in more around ITIL, ITSM, or PM Processes and PM tools then poke around the site and #LearnNOW.
A lot of things need to occur to get a project started. For the project manager, understanding the basics about the project – the goal, timing, budget are some of the tasks to getting organized. Included in that understanding is who will do what tasks for the project.
A great way to get organized and develop that overall understanding about the make up of a project is to document. No, really, it is. There are several basic documents that come to mind. As separate and distinct files, those include the scope,charter, schedule and raci matrix. Each of these is important for upfront planning and also during execution of the project. I have found that writing or contributing to each of these is very helpful. Being able to communicate the knowledge of the what, how and who during a project kick-off meeting helps get the team up to speed quickly. Most…
View original post 472 more words