2010 ESRI UC "10 Things to know about GIS Project Management"

The 2010 ESRI UC is a wonderful experience for any avid GISer.  You get saturated with GIS knowledge, and use cases.  It can be overwhelming if you don't have a plan.  One session that I planned on attending weeks before I arrived was "10 Things to know about GIS Project Management"

This presentation was given by ESRI Senior Project Managers, Gerry Clancy (21 years with ESRI) and Glenn Berger.  If you have the time, I _sincerely _encourage you to watch the video from start to finish.  Below the video, I've paraphrased the presentation from my notebook if you don't have time to listen to the whole video.

This was by far my most valuable take-away from the conference.

 Courtesy of ESRI1.     Define a clear vision and success criteriaa.       Identify your championb.      Define “what you are trying to build”c.       How does the client define success?d.      Are you creating a new process or replacing one?2.       Identify and Involve Stakeholdersa.       Who is funding this?b.      Who will be impacted?c.       Who will provide resources?d.      Who will determine success?e.      Decision Makers?f.        Who does not support the project?g.       Engage these people early and often3.       Gather Requirementsa.       Place requirements in contextb.      Conduct interviews & workshops                                                               i.      w/IT/end-users/project managersc.       Model the existing “as-is” processd.      Model the future business process                                                               i.      How can it be streamlined?                                                             ii.      Validate asap                                                            iii.      How will the future business process interact w/ other systems?e.      Do not be judgemental                                                               i.      Prioritize                                                             ii.      Break things into manageable chunks w/Functional, Data, and Non-functional meetings4.       Manage Changea.       Pay attention to scope, budget, and time5.       Identify and Monitor Risksa.       Internal/External Staffb.      Software Release Schedulesc.       Hardware Failures6.       Use a phased implementation approach (agile)a.       4,8,12 week incrementsb.      Use Project Management Software (MS Project)7.       Promote Communicationa.       Create a communication plan8.       Do not get enamored with the technologya.       Remember what you are trying to deliver (be careful of shiny objects!)9.       Engage the IT department (key stakeholders)a.       Understand policy and standardsb.      Hardare & Network impactsc.       Security Modeld.      Who will support the system?e.      Plan to educate and train the staff10.   Keep it simplea.       Identify the business rhythms and processesb.      Design and build for the 90% use case, not the 10%c.       Don’t reinvent the wheelLinks Original Video from Conference Proceedings