Bright Work
Prepared for XYZ Company
Juan M Garza, Senior Consultant Month , Date 2012
Agenda/Contents
1. BrightWork Overview
2. Strategy and Planning
3. Infrastructure
4. Training
5. Design, Build, Verify
6. Rollout
What is the BrightWork Tool?
►A mature application managing work and projects on the
SharePoint 2007 and 2010 platforms
►pmPoint - Process driven work and project management
►ISG has defined a standard PM management framework which
complements its PMO standard processes and templates
►Should you require a custom solution, pmPoint lets you decide
the level of management and structure required-the more
customization implemented, the greater the deployment time
►Templates and reporting to manage work, tasks, projects,
project offices and portfolios (Optional import / export / sync with Microsoft Project)
Deployment Strategy & Process
1. Strategy & Planning
Define the short and long term approach to
project management
2. Infrastructure
Get proper infrastructure in place and any needed
software installed
3. Training
Understand the feature set and how to
maintain the ongoing deployment
5. Rollout
Introduce the project management processes and associated tools and provide support for the
total solution.
Design
Build Verify
4. Design, Build, Verify Configure the templates and site hierarchies for the processes to be
implemented in this iteration and have them reviewed by the key
Infrastructure Setup
1. Ensure the correct SharePoint Infrastructure is in place
Review Pre-installation checklist in Install Guide
Ensure the correct SharePoint Infrastructure is in place Refer to the System Requirements in the Install Guide
2. Ensure that SharePoint is performing properly before
BrightWork is deployed—not much point in deploying BrightWork to a server that is under pressure with the existing workload.
Infrastructure Setup – (cont).
3. Install BrightWork
The install guide is very detailed with:
Pre-install check list
Install steps
*The latest version of the BrightWork software and the install guide can be found in Product &Templates Download*
4. Create an ISG BrightWork site collection
This is an ISG-defined SharePoint site collection, with all core BrightWork project management capabilities enabled
5. Carry out the post-install check list
6. Install supplementary templates as desired from the
Train Design & Build Team – SharePoint & BrightWork
►Some customers have virtually no SharePoint exposure. In
these cases it is wise to train the Customer design team in the basics of SharePoint, so they can actively participate in the upcoming design.
►Train the Customer design team using the relevant set of
Design, Build, Verify – The Approach
►Many common clichés apply:
Rome was not built in a day
Process improvement is a journey, not a destination
Continuous improvement is better than delayed perfection The more feedback you get on the early designs the
better—there is no ‘undo’ button in SharePoint
►Be agile; sometimes less is more.
It is very often better to implement a small piece of project management really well and very quickly – and get feedback sooner.
Design, Build, Verify
The goal of the Design, Build, Verify phase is to shape the
deliverables decided on in current iteration’s Strategy & Planning phase.
Design: choosing the most appropriate template(s) with which to start and decide what configurations will be applied
Build: configuration of the templates and reports according to the design.
Verify: collaborating with key stakeholders at set milestones to review and validate the latest design work before
Be Mindful of the Possible End-State Hierarchy Project Office Projects Templates Operations WorkOffice IT Project Office Operations Production Operations Production Operations Work IT Production IT Production IT Project Requests Marketing
Project Office Marketing
Production Marketing Production Marketing Project Work Manager Template Project Office Template IT Project Manager Template Project Requests Project Request Manager Support Requests
Work and Project Management Site Collection
Design > Build > Verify
►Host regular internal design reviews with the extended team.
►Verify the design with key stakeholders, especially
Contributors (team members) and Consumers (upper management). See next slide.
►Perform a design approval review before rollout.
Design Build Internal
Review Verification
Prepare for Rollout
►The goal of the Rollout phase is to prepare for the introduction
of BrightWork to the production environment.
►It includes:
Rollout planning (who gets access to what when and how) Loading initial data (projects, people)
Finalizing documentation (e.g. training materials)
Preparing and delivering training to users – including Project Management refresher training (if needed)
►Rollout can also involve the post-production tweaking of
templates and reports in response to unforeseen
requirements that often come to the forefront only when the solution is introduced to a wider audience and supplied with a broad range of project information.
Deployment Process
1. Strategy & Planning
Decide the short and long term approach
to project management
2. Infrastructure
Get proper infrastructure in
place and any needed software
installed
3. Training
Understand the feature set and how
to maintain the ongoing deployment 5. Rollout Introduce the adjusted project management process
and associated tool support and provide
support for the solution.
Design
Build Verify
4. Design, Build, Verify Design the templates and site hierarchies for the processes to be implemented in this iteration
and have them reviewed by the key stakeholders.
DEMO of BrightWork Tool
How long does deployment take?
►Many BrightWork customers use an agile approach that breaks the
deployment into a number of iterations; each delivers incremental value: Iteration 1 – Core Project Management (approve, control, report)
Iteration 2 – Enterprise-wide Project Management Office (PMO) Iteration 3 – Project Request / Demand Management
►Each iteration typically takes a minimum of 12 weeks and the factors that influence deployment duration are:
The gap between current project management oversight today versus the “to be” PM model implemented in each BrightWork iteration
Infrastructure readiness and compatibility
Management response and decision-making cycle time
Client resource preparedness (SharePoint/BW skill level) and availability Constraints defined by client organizations
Project Office Deployment Steps
1. Plan this deployment (Typical required effort … 3-5 days with executive approval additional)
2. Infrastructure / Technical Setup
Install BrightWork (on SharePoint) (Typical required effort per site … a few days to one week)
Create an ISG BrightWork Site Collection (Typical required effort per site… a few days to four weeks)
3. Train the Design & Build team (assumes SharePoint experienced users at start of training) (Typical required effort … volume/capacity dependent; approx. two days per individual)
4. Configure Project Office
Configure templates (minimal effort for standard implementations)
Apply security; populate groups and validate permissions (Typical required effort … 4-8 weeks)
Verify the configuration of BrightWork with key stakeholders
5. Rollout (Typical required effort … 3-5 days)
Create site documentation/Local BrightWork work instructions Provide training to client PMs, support staff, and key stakeholders
