Greg Kiefer - project management and share point 2010
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
960
On Slideshare
960
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
28
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • THIS SHOULD BE YOUR FIRST SLIDE
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 it’s the most recent version. A team can also organize it according to how their sponsor would like to see the log.
  • 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 to’s” 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.
  • 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.
  • 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.
  • THIS SHOULD BE YOUR SECOND TO LAST SLIDE – Encourage everyone to attend and remind them that BJs Brewhouse is just a few blocks up Bidwell from Three Stages
  • THIS SHOULD BE YOUR LAST SLIDE – Please ensure to leave this on as people are walking out and you’re wrapping things up. Thanks so much!

Transcript

  • 1. Welcome to the First Annual
    SharePoint Saturday
    Sacramento!!
  • 2. Project Management: Leveraging SharePoint
    Lessons Learned from Real Projects
  • 3. Who am I?
    • Project Management Professional
    • 4. Published author
    • 5. President/CEO Kiefer Consulting
    • 6. Advisory board member – GTC, Governor’s Small Business Advocacy Group, Powerhouse Science Center steering committee, and CIO Academy advisory committee
    • 7. Teaches Project Management Institute examination preparation courses
    • 8. Participated in the delivery of over 700 software applications
    • 9. International speaker – SOA, EA, PM Best Practices, Software Design Patterns…
    Greg Kiefer
  • 10. Who are you?
  • Agenda
    • SharePoint Project Management Best Practices
    • 15. What is a project as it relates to SharePoint?
    • 16. Project success factors
    • 17. Consequences of poor project management
    • 18. What are you trying to accomplish?
    • 19. Why use SharePoint?
    • 20. SharePoint Implementations
    • 21. What happens when you finish the project?
    5
  • 22. 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.”
    Wikipedia
    • Does this definition change when you leverage SharePoint?
    • 23. What aspects of the project can be applied to SharePoint?
    6
  • 24. Project Success Factors
    • Senior management commitment
    • 25. A clear understanding of the scope and key milestones
    • 26. Clear project requirements and specifications
    • 27. A comprehensive project plan
    • 28. Commitments and accountability from all stakeholders
    • 29. Accurate reporting of the project status
    • 30. A critical assessment of the risks and issues inherent in the project
    • 31. Clear and concise communications
    • 32. Plans, plans, plans…
    7
  • 33. Consequences of Poor Project Planning
    Marc Hirshfield, MBA, PMP, Vitalize Consulting Solutions
    • Organizational priorities are not met
    • 34. Over budget
    • 35. Low team morale
    • 36. Confusion among resources
    • 37. High resource turnover
    • 38. Unclear communication
    • 39. Missed dates
    Marc Hirshfield, MBA, PMP, Vitalize Consulting Solutions
  • 40. What are you trying to accomplish?
    9
  • 51. Why use SharePoint?
    10
  • 62. Project Management and Collaboration
    Project Samples
  • 63. Project Home Site
    Clearly identify the project objectives.
    Make the information easy to find.
    Who are the key players ?
  • 64. Questions
    What is missing from the team site?
    • Reference documents
    • 65. Issues & Risk Logs
    • 66. Key performance indicators (KPIs)
    Goals
    Make it easy to find information.
    Accountability, efficiency
  • 67. Project Home Site
    Who are the key contacts for your project?
    SharePoint 2010 allows multiple calendar views
    Execute SP Home
  • 68. Project Home Site
    SharePoint allows you to add all the important group information right on the home page for all members to have quick and easy access.
    Enriching Home
  • 69. Best Practices
    Is it better to spend time after the project is over to capture the lessons learned? Why not capture them throughout the project?
    • Create a content type for lessons learned categorization to be used throughout the project
    • 70. Create workflows to categorize information
    • 71. Create workflows to updates meta data (status, SLAs…)
    • 72. Leverage the list rating system. One to five star
    • 73. Leverage email (records management) integration so the project related information stored in your email repository is ported to SharePoint so it becomes an organizational asset.
  • Document Management
    It’s good to use metadata that allows you to filter your document library making things easier to find
    Knowing and being able to filter by type will also help findability.
    SharePoint allows you to upload one document and have multiple people working on it, and updates automatically after saving.
    Enriching Collaborations document library
  • 74. Project Communication
    Using specific metadata allows the Project Manager to know more about group communication.
    Grouping communications by date allows a Project Manager to see when communication has occurred.
    SharePoint is more effective at documenting/tracking logs than excel or word.
    Execute SP communication log
  • 75. Project Plan
    Use the built in Gantt chart to communicate the high-level deliverables and task assignments
    Sleepy Snoopies SharePoint Gantt Chart
  • 76. Integration
    • Leverage Project professional to synchronize your project schedules with your project team site.
    • 77. Use team foundation server (TFS) to manage team tasks, software development, testing by exposing the information in SharePoint via TFS web parts.
  • Calendar
    Your
    All of your team members can load their calendars in the same place to ease scheduling processes.
    PMG Schedule
  • 78. Team Profiles
    Good to add links to all site pages for ease of use.
    Understand your audience when applying themes to your site.
    Execute SP Profile Page
  • 79. Wikis
    Leverage Metadata data throughout the site.
    Grouping terms helps usability/findability.
    Creating links for each term helps site organization and look and feel.
    Execute SP Project Terms
  • 80. Additional Samples
    Project Terms
    https://extranet.kieferconsulting.com/sites/csus/tpps/Wiki/Home.aspx
    Lessons Learned
    https://extranet.kieferconsulting.com/sites/csus/tpps/Lessons%20Learned/Home.aspx
    Project Schedule
    https://extranet.kieferconsulting.com/sites/csus/tothepoint/Lists/Project%20Plan/gantt.aspx
    Issue Log
    https://extranet.kieferconsulting.com/sites/csus/Team_Phoenix/Lists/Issues%20Log/AllItems.aspx
    Risk Log
    https://extranet.kieferconsulting.com/sites/csus/Team_Phoenix/Lists/Risk%20Log/AllItems.aspx
    https://extranet.kieferconsulting.com/sites/csus/Sacramento6/Lists/Risk%20Log/AllItems.aspx
    Team Member Profiles
    https://extranet.kieferconsulting.com/sites/csus/tpps/sitepages/about.aspx
    Office 365
    https://kieferconsulting.sharepoint.com
  • 81. Project Close-out
    • What do you do with the project artifacts?
    • 82. When does a project artifact become a record?
    • 83. How do you leverage your project site for future projects?
    • 84. Where do you store lessons learned information?
    • 85. What should be the overall taxonomy for the site?
    • 86. Did you leverage workflows to ensure accountability?
    25
  • 87. Conclusion
    • SharePoint can be used to improve all aspects of communication for a project.
    • 88. Remember to train your team and stakeholders on the technology.
    • 89. Apply new features to improve communications, such as, wikis…
    • 90. Call me anytime
    26
  • 91. Contact Us
    http://www.facebook.com/pages/KIEFER-CONSULTING-INC
    http://www.linkedin.com/company/kiefer-consulting
    www.kieferconsulting.com
    www.sharepointdesigncenter.com
    http://twitter.com/kieferweb
  • 92.
  • 93. Don’t Forget
    SharePint!!
    Sponsored By…..
    Join us at 6:00 pm at BJs Brewhousefor a free drink, kindly provided by Rackspace! A great opportunity to network with other SharePoint Professionals!
    Don’t forget to fill out your bingo cards and surveys to be eligible for GREAT end of day raffles!
  • 94. Thanks to Our Sponsors