Book contents
- Frontmatter
- Contents
- List of figures and tables
- Acknowledgements
- The authors
- List of abbreviations
- Series Editor's introduction
- Introduction
- Section 1 Theories
- Section 2 Infrastructure
- Section 3 Activities and tools
- 34 Action learning sets
- 35 Apprentices, graduate trainees and work placements
- 36 Awards
- 37 Buddying
- 38 CILIP qualifications
- 39 CILIP qualifications – revalidation
- 40 Coaching
- 41 Collaborative working
- 42 Communities of practice – internal
- 43 Communities of practice – external
- 44 Conferences – attending
- 45 Conferences – organizing
- 46 Conferences – posters
- 47 Conferences – presenting
- 48 Conferences – sharing the learning
- 49 Conferences – volunteering
- 50 Conferences – workshops
- 51 Conferences – writing proposals for papers
- 52 CVs
- 53 Exchange of Experience events, TeachMeets and Unconferences
- 54 Formal qualifications
- 55 Funding for CPD
- 56 Group conversations
- 57 Job rotation
- 58 Learning logs and journals
- 59 Meetings – attending
- 60 Meetings – chairing
- 61 Meetings – note taking
- 62 Mentoring – external
- 63 Mentoring – peer
- 64 Minutes of madness
- 65 MOOCs
- 66 Networks
- 67 Networks – setting up
- 68 Networks – running
- 69 Personal development plans
- 70 Presentations – general tips
- 71 Professional membership
- 72 Projects
- 73 Project management tools
- 74 Reflection – facilitating
- 75 Reflective practice
- 76 Reflective writing
- 77 Research activities
- 78 Secondments
- 79 Shadowing
- 80 Social media
- 81 SWOT analysis
- 82 Time management
- 83 Time management tools
- 84 Training courses – attending
- 85 Training courses – commissioning
- 86 Training courses – planning, delivering and evaluating
- 87 Twitter
- 88 Twitter chats
- 89 VLEs
- 90 Visits
- 91 Volunteering
- 92 Webinars
- 93 Writing blog posts
- 94 Writing business cases
- 95 Writing case studies
- 96 Writing e-mails
- 97 Writing journal articles
- 98 Writing newsletters
- 99 Writing procedures
- 100 Writing project plans
- 101 Writing reports
- Index
100 - Writing project plans
from Section 3 - Activities and tools
Published online by Cambridge University Press: 09 June 2018
- Frontmatter
- Contents
- List of figures and tables
- Acknowledgements
- The authors
- List of abbreviations
- Series Editor's introduction
- Introduction
- Section 1 Theories
- Section 2 Infrastructure
- Section 3 Activities and tools
- 34 Action learning sets
- 35 Apprentices, graduate trainees and work placements
- 36 Awards
- 37 Buddying
- 38 CILIP qualifications
- 39 CILIP qualifications – revalidation
- 40 Coaching
- 41 Collaborative working
- 42 Communities of practice – internal
- 43 Communities of practice – external
- 44 Conferences – attending
- 45 Conferences – organizing
- 46 Conferences – posters
- 47 Conferences – presenting
- 48 Conferences – sharing the learning
- 49 Conferences – volunteering
- 50 Conferences – workshops
- 51 Conferences – writing proposals for papers
- 52 CVs
- 53 Exchange of Experience events, TeachMeets and Unconferences
- 54 Formal qualifications
- 55 Funding for CPD
- 56 Group conversations
- 57 Job rotation
- 58 Learning logs and journals
- 59 Meetings – attending
- 60 Meetings – chairing
- 61 Meetings – note taking
- 62 Mentoring – external
- 63 Mentoring – peer
- 64 Minutes of madness
- 65 MOOCs
- 66 Networks
- 67 Networks – setting up
- 68 Networks – running
- 69 Personal development plans
- 70 Presentations – general tips
- 71 Professional membership
- 72 Projects
- 73 Project management tools
- 74 Reflection – facilitating
- 75 Reflective practice
- 76 Reflective writing
- 77 Research activities
- 78 Secondments
- 79 Shadowing
- 80 Social media
- 81 SWOT analysis
- 82 Time management
- 83 Time management tools
- 84 Training courses – attending
- 85 Training courses – commissioning
- 86 Training courses – planning, delivering and evaluating
- 87 Twitter
- 88 Twitter chats
- 89 VLEs
- 90 Visits
- 91 Volunteering
- 92 Webinars
- 93 Writing blog posts
- 94 Writing business cases
- 95 Writing case studies
- 96 Writing e-mails
- 97 Writing journal articles
- 98 Writing newsletters
- 99 Writing procedures
- 100 Writing project plans
- 101 Writing reports
- Index
Summary
Writing project plans
THE PLANNING PROCESS is a crucial activity for any project to be successful and developing your staff in this area is vital to ensuring that your service grows and adapts to change. Effective project planning ensures that outcomes are delivered on schedule and within budget and that everyone involved knows what is expected of them. In this Tip we will discuss developing the initial project brief and the creation of project plans, which should be monitored throughout the lifetime of the project.
The brief
The project brief or specification is sometimes called a project implementation document (PID) or a project charter, and this will be informed by the project management approach that is used (Mind Tools, 2016). Whatever you call this document, it will clearly define the project proposal and intended outcomes, including as much detail as possible. If the parameters of the project are not clearly outlined from the outset, this will contribute to the project's not being completed or failure to achieve the intended outcomes (Young, 2013). It is therefore essential that all resource requirements, timescales, team roles and limitations are described in detail from the beginning. The entire project team and all relevant stakeholders must be involved in developing the brief, to mitigate misunderstandings and to manage expectations. Involving the entire project team in the planning process and securing agreement about their roles and the project outcomes means that the project is more likely to succeed and individuals are more likely to commit to fulfilling their responsibilities.
There is no single approach to presenting a project brief, and to some extent this will be dictated by your organization, the methodology you use and the size of the project. As a minimum, your project brief should answer the following questions (Young, 2013; Mind Tools, 2016):
• Why is the project needed?
• What is the scope of the project?
• What are the boundaries of the project?
• What are the principal objectives?
• Who are the key stakeholders?
• What resources are needed?
• How much will it cost?
• Who needs to be involved and what are their roles?
• What risks have been identified?
• What is the expected output or outcome?
• How long will the project take?
- Type
- Chapter
- Information
- Practical Tips for Developing Your Staff , pp. 266 - 269Publisher: FacetPrint publication year: 2016