Skip to main content
Top

2010 | Book

Pro Project Management with SharePoint 2010

Author: Mark J. Collins

Editors: Jonathan Hassell, Steve Anglin, Mark Beckner, Ewan Buckingham, Gary Cornell, Jonathan Gennick, Jonathan Hassell, Michelle Lowman, Matthew Moodie, Duncan Parkes, Jeffrey Pepper, Frank Pohlmann, Douglas Pundick, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh, Corbin Collins, Damon Larson

Publisher: Apress

insite
SEARCH

About this book

Many successful project managers are beginning to utilize Microsoft SharePoint to drive their projects and operational initiatives. SharePoint Server provides teams with a centralized location for project information and facilitates collaboration between project team members. The intention of this book is to provide a hands-on case study that you can follow to create a complete project management information system (PMIS) using SharePoint Server 2010.

Each chapter is focused on a typical project management activity and demonstrates techniques that can be used to facilitate that activity. The book covers all project phases from managing requirements, implementation, testing and post production support. By the end of the book you’ll have a toolbox full of solutions and plenty of working examples. With these you’ll be able to build your own PMIS uniquely suited to your organization.

Table of Contents

Frontmatter

Introduction

Chapter 1. Introduction
Abstract
The primary activity of project managers is to keep track of information. Work items are completed, milestones are achieved, defects are reported, tests are passed ... and the list goes on. More than simply capturing this information, project managers need to analyze this data and provide meaningful status reports. SharePoint is uniquely suited to this environment. As you&ll see throughout this book, SharePoint can be used as a repository for all of these project management artifacts. Using a combination of web and Microsoft Office applications, you can provide easy access to enter, view, and report on your project data.
Mark J. Collins

Requirements

Frontmatter
Chapter 2. Collecting Requirements
Abstract
In this chapter, you&ll create a simple list that will be used to track requirements. The remaining chapters in this section will add more capabilities to this list.
Mark J. Collins
Chapter 3. Processing Incoming E-mail
Abstract
In this chapter you&ll provide a facility that allows individuals the ability to contribute to the requirement-gathering process by simply sending an e-mail.
Mark J. Collins
Chapter 4. Managing Requirements
Abstract
In this chapter you&ll enhance the Requirements list that you created in Chapter 2. First, you&ll implement a way to score each requirement. This will provide a quantitative approach for determining which requirements should be implemented first. Then you&ll add a feature to specify dependencies since some requirements will rely on other related requirements. With these enhancements you&ll be able to more easily plan the project and decide which requirements are in scope.
Mark J. Collins
Chapter 5. Supporting Discussions
Abstract
Often during the requirement-gathering process there can be negotiation between individuals before arriving at the final requirement. While the final result is the primary artifact used for managing the project, sometimes the internal discussion can be a useful reference. In this chapter I&ll show you how to add discussions to your SharePoint site. Specifically, you will do the following:
Mark J. Collins

Managing Development

Frontmatter
Chapter 6. User Stories
Abstract
In this chapter you&ll provide a facility for defining user stories, which is a handy technique for capturing the functionality of the project. I&ll first explain what user stories are and then show you how to create a SharePoint list to store them.
Mark J. Collins
Chapter 7. Project Backlog
Abstract
In the last chapter you created a User Stories list, which you&ll use to collect the features of the project. Once these have all been identified, the collection of user stories will now be the definition of the work to be done. In this chapter you&ll begin using these to start planning the project.
Mark J. Collins
Chapter 8. Iteration Backlog
Abstract
The iteration backlog is the primary tool that the development team uses to manage its activities. In this chapter, you&ll add an iteration backlog to your SharePoint site.
Mark J. Collins
Chapter 9. Burndown Charts
Abstract
In the previous chapters you provided mechanisms for organizing the project, breaking it down into relatively short iterations and then planning the activities of the current iteration. In this chapter, you&ll implement facilities for tracking progress, both for the current iteration as well as the overall project. You will also build a developer&s portal page that will include most of the features of your SharePoint site that developers will use on a daily basis.
Mark J. Collins

Testing

Frontmatter
Chapter 10. Getting Organized
Abstract
In this chapter, I&ll show you some useful techniques for organizing information in SharePoint. This is a very brief introduction to SharePoint, but it will get you started with some of the more useful features.
Mark J. Collins
Chapter 11. Creating Test Cases
Abstract
In this chapter, you&ll build the test cases that will be used to verify your project. Defining a set of test cases to verify all of the requirements can be a daunting task. I&ll explain some techniques that should help you accomplish this, and later in the chapter I&ll show you how to capture the test cases in a SharePoint list.
Mark J. Collins
Chapter 12. Reporting Defects
Abstract
In this chapter you&ll provide a facility for defining a test cycle, which is a set of test cases that are to be performed against a specific release. You will then use this to record the test results.
Mark J. Collins
Chapter 13. Testing Metrics
Abstract
In this chapter I&ll present several metrics that will help communicate the testing progress and provide some indications as to the overall quality of the project. Then I&ll show you how to add these to your SharePoint site.
Mark J. Collins

Postproduction

Frontmatter
Chapter 14. Workflow Tasks
Abstract
In this chapter you&ll begin building a workflow to handle the postproduction requests. These could be defects that need to be corrected, support questions, or enhancements that should be considered for future releases. The basic concepts introduced here can be used in other types of requests as well.
Mark J. Collins
Chapter 15. State Machine Workflows
Abstract
In the previous chapter I presented the design of an issue-tracking system and you created the lists and content types that will be used. In this chapter you will implement the workflow logic using a state machine workflow.
Mark J. Collins
Chapter 16. Creating Custom Forms
Abstract
In the previous chapter you implemented a task-based tracking system using a state machine workflow. When an item was added to the Issues list, the workflow took over, generating tasks according to the business rules. The participants performed the tasks assigned to them as the issue progressed through the workflow. The Tasks list and the individual task forms are the primary interface to this system.
Mark J. Collins
Backmatter
Metadata
Title
Pro Project Management with SharePoint 2010
Author
Mark J. Collins
Editors
Jonathan Hassell
Steve Anglin
Mark Beckner
Ewan Buckingham
Gary Cornell
Jonathan Gennick
Jonathan Hassell
Michelle Lowman
Matthew Moodie
Duncan Parkes
Jeffrey Pepper
Frank Pohlmann
Douglas Pundick
Ben Renow-Clarke
Dominic Shakeshaft
Matt Wade
Tom Welsh
Corbin Collins
Damon Larson
Copyright Year
2010
Publisher
Apress
Electronic ISBN
978-1-4302-2830-1
Print ISBN
978-1-4302-2829-5
DOI
https://doi.org/10.1007/978-1-4302-2830-1

Premium Partner