際際滷

際際滷Share a Scribd company logo
Project Management with SharePoint 2010
Project Management: Leveraging SharePointLessons Learned from Real Projects
Who am I?Project Management Professional
Published author
President/CEO Kiefer Consulting
Advisory board member  GTC,  Governors Small Business Advocacy Group, Powerhouse Science Center steering committee, and CIO Academy advisory committee
Teaches Project Management Institute examination preparation courses
Participated in the delivery of over 700 software applications
International speaker  SOA, EA, PM Best Practices, Software Design PatternsGreg Kiefer
AgendaSharePoint Project Management Best Practices
What is a project as it relates to SharePoint?
Project success factors
Consequences of poor project management
What are you trying to accomplish?
Why use SharePoint?
SharePoint  Implementations
What happens when you finish the project?4
What is a project?A project is a temporary endeavor, having a defined beginning and end, undertaken to meet unique goals and objectives, usually to bring about beneficial change or added value.								WikipediaDoes this definition change when you leverage SharePoint?
What aspects of the project can be applied to SharePoint?5
Project Success FactorsSenior management commitment
A clear understanding of the scope and key milestones
Clear project requirements and specifications
A comprehensive project plan
Commitments and accountability from all stakeholders
Accurate reporting of the project status
A critical assessment of the risks and issues inherent in the project
Clear and concise communications
Plans, plans, plans6
Consequences of Poor Project PlanningMarc Hirshfield,  MBA, PMP, Vitalize Consulting Solutions Organizational priorities are not met

More Related Content

Project Management with SharePoint 2010

Editor's Notes

  1. THIS SHOULD BE YOUR FIRST SLIDE
  2. Microsoft has made it easy to install and get it up and running, but that undercuts the lifecycle work that needs to take place: strategy & planning, requirements, information assessment, enterprise information architecture, design, prototyping, development and education.
  3. Microsoft has made it easy to install and get it up and running, but that undercuts the lifecycle work that needs to take place: strategy & planning, requirements, information assessment, enterprise information architecture, design, prototyping, development and education.
  4. Microsoft has made it easy to install and get it up and running, but that undercuts the lifecycle work that needs to take place: strategy & planning, requirements, information assessment, enterprise information architecture, design, prototyping, development and education.
  5. Microsoft has made it easy to install and get it up and running, but that undercuts the lifecycle work that needs to take place: strategy & planning, requirements, information assessment, enterprise information architecture, design, prototyping, development and education.
  6. Microsoft has made it easy to install and get it up and running, but that undercuts the lifecycle work that needs to take place: strategy & planning, requirements, information assessment, enterprise information architecture, design, prototyping, development and education.
  7. SharePoint helps you manage documents easier. There is always only one version with SharePoint, which is readily available to all group members. Each member can make edits and save it. This new saved version is the one that shows up in the library for other team members to view/edit. You can also keep all project documents in the same library. By using columns (metadata) you can attach important document information. This is used to filter through documents to make findability easier. (i.e.) So you could search for a document by the role, business analyst, and the type of document it is, excel file. This would filter your search to only show, KCI Risk Log as listed above.
  8. SharePoint lists can be organized to show the most recent event to be displayed first. It also is a centralized place where everyone can update the log without needing to check if its the most recent version. A team can also organize it according to how their sponsor would like to see the log.
  9. A wiki is a place to keep important project information or things people might often have questions about. Definitions tend to be a great use for wikis. Also, how tos within SharePoint are another good reason to have a wiki. This is a great wiki because it allows you to organize the information by type of definition (certification/project term/etc). The titles of the columns allow you to filter the information by the options available within the column. For this, the reference column would have been more useful if the options within it were project manager/business analyst/etc. This is because then you can look in certificates, and then search specifically for project management ones instead of having to know what all of the acronyms mean.
  10. Microsoft has made it easy to install and get it up and running, but that undercuts the lifecycle work that needs to take place: strategy & planning, requirements, information assessment, enterprise information architecture, design, prototyping, development and education.
  11. Microsoft has made it easy to install and get it up and running, but that undercuts the lifecycle work that needs to take place: strategy & planning, requirements, information assessment, enterprise information architecture, design, prototyping, development and education.
  12. THIS SHOULD BE YOUR SECOND TO LAST SLIDE Encourage everyone to attend and remind them that the Daily Pint is just a few blocks up Pico from SMC (North East)
  13. THIS SHOULD BE YOUR LAST SLIDE Please ensure to leave this on as people are walking out and youre wrapping things up. Thanks so much!