e-Mail: Password: Forgotten password
Affordable world class business and ICT (/ IT) services for organisations of all sizes.
Logo



Web Briefcase Ltd Registered in
England & Wales
Reg no: 05393683
©2013-2017
Selected Records
   

Project Services

Table icon Services

Parent:
\Business Services
Organisation:
\Web Briefcase Ltd
Description:
webBRIECASE project services include project, programme and portfolio management. Also Project Management Office (PMO) Services.


Services

Export
All|0|1|2|3|4|5|6|7|8|9
|A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z

A BRIEF provides a (hopefully) single page description of a work stream (project, programme, portfolio) sufficent for a stakeholder to determine and approve the purpose, scope and expected outcomes of the project.

A brief is an essential requirement of a work stream since it is an input into knowledge area plans (e.g. Time Management Plan) and can be used to avoid scope creep / leap. Any significant changes to the work stream should be registered with a project change request and a review of the brief.

The brief includes:

  • The background summary can be shown in project portfolio lists alongside the work stream name.
  • SMART (specific, measurable, agreed upon, reastlic, time-based) objectives defined what strategic corporate objectives the project aims to align with.
  • Scope inclusions and exclusions are defined to define the scope boundaries of the work streams influence. These include included and excluded: geography, groups (directorates, teams, etc), roles, systems, etc.
  • Potential restrictions and causes of failure are listed as constraints: risks, issues, dependencies, deadlines, etc.
  • Assumptions are listed, to be proven / disproven and dealt with accordingly.
  • The resources required for the work stream are identified: budget, staffing, materials, etc.
  • Deliverables include: (ITIL aligned) service model, product descriptions, packaging, etc.

webbRIEFCASE can facilitate the preparation of a robust work stream brief as follows:

  1. Initial meeting with the project sponsor with subseequent write-up.
  2. Meeting with the project sponsor, senior customer and (optionally) other customers with subsequent write-up.
  3. Meeting with the project executive (when appointed) to approve the brief.

The facilitation and documentation work is charged on an hourly basis. Contact support@webBRIEFCASE.com for more information or to order.

A webBRIEFCASE approved brief (whether prepared by you or webbRIEFCASE) is required in order for webBRIEFCASE to manage a work stream (project, programme or portfolio) for you.


A BURNDOWN CHART is a graph which presents the expected and actual burndown (product task completion) rate of a sprint or project, product backlog. The product backlog lists a breakdown of tasks from the project deliverables defined in the project brief.

The webBRIEFCASE Excel Burndown Chart Tool is available on request from support@webBRIEFCASE.com for just £5 + VAT / person (e.g. project manager / project co-ordinator) / year and includes e-mail and Skype support.


A programme is a collection of projects. webBRIEFCASE will set-up a programme as necessary. It is unlikely that a client will need to request a programme.


Define the project Terms and Reference (ToR). One method is to define the BOSCARD: background, objectives, scope (inclusion / exclusion), constraints, assumptions, resources and deliverables.


A project schedule developed in Microsoft Office Project to determine an estimated completion date of activities. Also, resource (people) assigned to tasks.

  • Preparation of the status update presentation (2 hours)
  • Distribution of the status update and dealing with responses (1 hour)
  • Meeting (1 hour)
  • Preparation and distribution of minutes (1 hour)
  • This one day of effort could be split across multiple days in a week. Any project execution of the actions from the meeting would require extra effort.&wB_action=show'> A project status update includes a description of the status (red, amber, green + description) of various aspects (knowledge areas) of the project, e.g. cash, HR, time (on track?), stakeholder engagement, etc. The description will be provided in a PowerPoint presentation and distributed before the status update meeting.

    A meeting will then take place to discuss the project, focussing on the content of the document, but also with an "any other business" section at the end.

    The document will be updated and distributed along with minutes. Of particular interest will be any follow-on actions.

    Estimates of time required.

    • Collection of information for the update (2 hours) - 1 hour meeting, and 1 hour to follow-up with those show couldn't attend the meeting
    • Preparation of the status update presentation (2 hours)
    • Distribution of the status update and dealing with responses (1 hour)
    • Meeting (1 hour)
    • Preparation and distribution of minutes (1 hour)

    This one day of effort could be split across multiple days in a week. Any project execution of the actions from the meeting would require extra effort.


    A RESPONSIBILITY MATRIX / ACCOUNTABILITY MATRIX (RACI) states very clearly which roles (and therefore people) are accountable, responsible, consulted and informed for project and operational processes and process steps. 

    webBRIEFCASE can facilitate the preparation of a robust RACI for your work stream (e.g. project), helping to identify the stakeholder roles - listed across the columns at the top of the matrix, and the processes / process steps listed down the rows of the matrix.

    Then assist in the identification of A (accountable), R (responsible), C (consulted) and I (informed) in the matrix cells.

    Once the RACI is prepared, a review session can ensure it is approved with the listed stakeholders. The RACI can then later be used to ensure people deliver against requirements by fulfilling their obligations where they are listed as accountable or responsible.

    A webbRIEFCASE approved project RACI (whether produced by you or webBRIEFCASE) is required for webBRIEFCASE to manage a project for you.


  • An assumption is something which is believed to be true, but needs to be confirmed either way. If the assumption is invalid, it could introduce an issue.
  • An issue is something which has happened. It would ideally have been previously identified as a risk. Issues should be prioritised and the impact dealt with.
  • A dependency identifies something which needs to happen in order for timely start / completion of one or more activities. A project (e.g. move people into a building) could be dependent on another project (e.g. prior rennovation of the building).
  • An opportunity identifies a chance to affect improvements in the work stream. An opportunity could be for example, use of a currently inactive staff member as a resource.
  • Risks, assumptions, issues and dependencies will often have a primarily negative impact on a work stream. Opportunities however, have a potential positive influence. It could be argued that opportunities should not be part of the risk register - however, the risk register receives repeating attention, and opportunities should be afforded similar attention.

    webBRIEFCASE can facilitate the comprehensive identification of risks for a work stream using a methodical approach. Contact support@webBRIEFCASE.com for more information.

    &wB_action=show'> Identification and appropriate management of risks is essential to avoid project failure. A risk register / RAID / RAIDO log is a place to record information about risks, issues, assumptions, dependancies and opportunities.

    • A risk is something which may happen but hasn't happened yet. Risks should be avoided / mitigated. If the risk trigger event has happened, the risk becomes an issue, to be dealt with accordingly.
    • An assumption is something which is believed to be true, but needs to be confirmed either way. If the assumption is invalid, it could introduce an issue.
    • An issue is something which has happened. It would ideally have been previously identified as a risk. Issues should be prioritised and the impact dealt with.
    • A dependency identifies something which needs to happen in order for timely start / completion of one or more activities. A project (e.g. move people into a building) could be dependent on another project (e.g. prior rennovation of the building).
    • An opportunity identifies a chance to affect improvements in the work stream. An opportunity could be for example, use of a currently inactive staff member as a resource.

    Risks, assumptions, issues and dependencies will often have a primarily negative impact on a work stream. Opportunities however, have a potential positive influence. It could be argued that opportunities should not be part of the risk register - however, the risk register receives repeating attention, and opportunities should be afforded similar attention.

    webBRIEFCASE can facilitate the comprehensive identification of risks for a work stream using a methodical approach. Contact support@webBRIEFCASE.com for more information.



    Service Category Services

    Export
    All|0|1|2|3|4|5|6|7|8|9
    |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z


    Service Category
    Record bullet \Business / Consultancy Services\Project Management
    Record bullet \Business / Consultancy Services\Project Management


    Powered by the webBRIEFCASE Toolkit