On any user-assistance or technical-communication project, the project plan - or Documentation Plan - is essential for aligning expectations of the documentation team and all other stakeholders. We explore the outline for the doc plan, the importance of the doc plan for validating your assumptions and for ensuring that your team will receive what it needs from other stakeholders, and a few best practices.
Technical Writing in Agile: New Approaches, New OpportunitiesLarry Kunz
Description of the agile development process, with an emphasis on how it affects the work of writers and project managers in technical communication. The final part of the presentation lists several opportunities or advantages that accrue to technical writers who begin working in agile.
Description of project management for technical documentation, with emphasis on how new trends -- specifically Web 2.0 and Agile -- are changing the process. Contains selected material from my presentation at the 2010 STC Summit, "Documentation Projects in a Collaborative World."
Technical Writing in Agile: New Approaches, New OpportunitiesLarry Kunz
Description of the agile development process, with an emphasis on how it affects the work of writers and project managers in technical communication. The final part of the presentation lists several opportunities or advantages that accrue to technical writers who begin working in agile.
Description of project management for technical documentation, with emphasis on how new trends -- specifically Web 2.0 and Agile -- are changing the process. Contains selected material from my presentation at the 2010 STC Summit, "Documentation Projects in a Collaborative World."
How to write a TUBITAK 1001 Research Project Proposal?Selcen Ozturkcan
How to write a successful TUBITAK 1001 research project proposal?
TUBITAK 1001 Proje Basvurusu nasıl hazırlanır?
by Assoc. Prof. Selcen Ozturkcan (Istanbul Bilgi University)
presented at TTO Event of Ozyegin University on Jan 2014
Training Slides of Introduction toTech Communication &Project Management, discussing the importance of Project Management.
For further information regarding the course, please contact:
info@asia-masters.com
www.asia-masters.com
Past, present, and future of scholarly technology and practicesAndrew Treloar
Thoughts about past, the present and the future of scholarly technologies and scholarly practices. Based on work done with @hvdsomp at #DANS, as well as discussions with @scharnhorsta
Having trouble developing your dissertation or thesis proposal? Its like skydiving... you're in control and choose where you go, but the hardest part is jumping off. This slideshow provides an overview of the proposal development process. This is a presentation developed through the Graduate Resource Center at the University of New Mexico.
(Exploratory) Testing with Scripted SupportSimon Morley
Some consideration and reflections on applying good software test thinking in signalling protocol environments using "agile" and incremental development models.
They're Coming! Combining Teams and Cultures in a Corporate MergerLarry Kunz
Your technical communication future will place against a backdrop of corporate change. This case study shows you the dynamics of combining diverse teams, workflows, and tool sets. Our management team worked to align corporate cultures, with an emphasis on empathetic listening and clear communication.
Working with distributed teams: How I learned to stop worrying and love WebExLarry Kunz
Describes differences between the office of yesterday, where everyone was located together and usually shared values, backgrounds, and institutional memory - and today's distributed work teams, where people never meet in person and come from a wide variety of backgrounds and expectations.
More Related Content
Similar to Setting expectations through the Doc Plan
How to write a TUBITAK 1001 Research Project Proposal?Selcen Ozturkcan
How to write a successful TUBITAK 1001 research project proposal?
TUBITAK 1001 Proje Basvurusu nasıl hazırlanır?
by Assoc. Prof. Selcen Ozturkcan (Istanbul Bilgi University)
presented at TTO Event of Ozyegin University on Jan 2014
Training Slides of Introduction toTech Communication &Project Management, discussing the importance of Project Management.
For further information regarding the course, please contact:
info@asia-masters.com
www.asia-masters.com
Past, present, and future of scholarly technology and practicesAndrew Treloar
Thoughts about past, the present and the future of scholarly technologies and scholarly practices. Based on work done with @hvdsomp at #DANS, as well as discussions with @scharnhorsta
Having trouble developing your dissertation or thesis proposal? Its like skydiving... you're in control and choose where you go, but the hardest part is jumping off. This slideshow provides an overview of the proposal development process. This is a presentation developed through the Graduate Resource Center at the University of New Mexico.
(Exploratory) Testing with Scripted SupportSimon Morley
Some consideration and reflections on applying good software test thinking in signalling protocol environments using "agile" and incremental development models.
They're Coming! Combining Teams and Cultures in a Corporate MergerLarry Kunz
Your technical communication future will place against a backdrop of corporate change. This case study shows you the dynamics of combining diverse teams, workflows, and tool sets. Our management team worked to align corporate cultures, with an emphasis on empathetic listening and clear communication.
Working with distributed teams: How I learned to stop worrying and love WebExLarry Kunz
Describes differences between the office of yesterday, where everyone was located together and usually shared values, backgrounds, and institutional memory - and today's distributed work teams, where people never meet in person and come from a wide variety of backgrounds and expectations.
As a technical communicator in today's interconnected world, technology makes it easy for you to work on a development team with members located all over the world. In much the same way, more and more of the technical content that we produce is used by people in other countries -- people who speak different languages, who come from different cultures, and who use different technology.
In this professional-development presentation, Larry Kunz describes the ways in which you can develop technical content so that it is more easily translated and so that it can be used easily by people all over the globe.
Building and Maintaining Your Personal BrandLarry Kunz
Your personal brand is your professional identity. It's up to you to create and cultivate it. Today's social media offer new opportunities and a new urgency for personal branding. Learn how your colleagues have built their personal brands, and discover how you can build an effective brand for yourself.
Best practices to help technical communicators work with subject-matter experts (SMEs) - including tips for interviewing, conducting reviews, and working cross-culturally.
The Future of Technical Communication (Future of #techcomm)Larry Kunz
Hear about trends that are shaping the technical communication (#techcomm) profession, discover the skills you'll need to succeed in the new world of #techcomm, and find out how your day-to-day work is changing.
Moving the Organization to Collaborative or Structured Authoring
Audience: Project managers and other technical communicators
Presented 25 April 2012 as part of STC webinar series
Outline:
- What is collaborative or structured authoring?
- The steps for planning and executing the transition from traditional authoring
- Putting it all into perspective
Digital Transformation and IT Strategy Toolkit and TemplatesAurelien Domont, MBA
This Digital Transformation and IT Strategy Toolkit was created by ex-McKinsey, Deloitte and BCG Management Consultants, after more than 5,000 hours of work. It is considered the world's best & most comprehensive Digital Transformation and IT Strategy Toolkit. It includes all the Frameworks, Best Practices & Templates required to successfully undertake the Digital Transformation of your organization and define a robust IT Strategy.
Editable Toolkit to help you reuse our content: 700 Powerpoint slides | 35 Excel sheets | 84 minutes of Video training
This PowerPoint presentation is only a small preview of our Toolkits. For more details, visit www.domontconsulting.com
"𝑩𝑬𝑮𝑼𝑵 𝑾𝑰𝑻𝑯 𝑻𝑱 𝑰𝑺 𝑯𝑨𝑳𝑭 𝑫𝑶𝑵𝑬"
𝐓𝐉 𝐂𝐨𝐦𝐬 (𝐓𝐉 𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬) is a professional event agency that includes experts in the event-organizing market in Vietnam, Korea, and ASEAN countries. We provide unlimited types of events from Music concerts, Fan meetings, and Culture festivals to Corporate events, Internal company events, Golf tournaments, MICE events, and Exhibitions.
𝐓𝐉 𝐂𝐨𝐦𝐬 provides unlimited package services including such as Event organizing, Event planning, Event production, Manpower, PR marketing, Design 2D/3D, VIP protocols, Interpreter agency, etc.
Sports events - Golf competitions/billiards competitions/company sports events: dynamic and challenging
⭐ 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐝 𝐩𝐫𝐨𝐣𝐞𝐜𝐭𝐬:
➢ 2024 BAEKHYUN [Lonsdaleite] IN HO CHI MINH
➢ SUPER JUNIOR-L.S.S. THE SHOW : Th3ee Guys in HO CHI MINH
➢FreenBecky 1st Fan Meeting in Vietnam
➢CHILDREN ART EXHIBITION 2024: BEYOND BARRIERS
➢ WOW K-Music Festival 2023
➢ Winner [CROSS] Tour in HCM
➢ Super Show 9 in HCM with Super Junior
➢ HCMC - Gyeongsangbuk-do Culture and Tourism Festival
➢ Korean Vietnam Partnership - Fair with LG
➢ Korean President visits Samsung Electronics R&D Center
➢ Vietnam Food Expo with Lotte Wellfood
"𝐄𝐯𝐞𝐫𝐲 𝐞𝐯𝐞𝐧𝐭 𝐢𝐬 𝐚 𝐬𝐭𝐨𝐫𝐲, 𝐚 𝐬𝐩𝐞𝐜𝐢𝐚𝐥 𝐣𝐨𝐮𝐫𝐧𝐞𝐲. 𝐖𝐞 𝐚𝐥𝐰𝐚𝐲𝐬 𝐛𝐞𝐥𝐢𝐞𝐯𝐞 𝐭𝐡𝐚𝐭 𝐬𝐡𝐨𝐫𝐭𝐥𝐲 𝐲𝐨𝐮 𝐰𝐢𝐥𝐥 𝐛𝐞 𝐚 𝐩𝐚𝐫𝐭 𝐨𝐟 𝐨𝐮𝐫 𝐬𝐭𝐨𝐫𝐢𝐞𝐬."
Putting the SPARK into Virtual Training.pptxCynthia Clay
This 60-minute webinar, sponsored by Adobe, was delivered for the Training Mag Network. It explored the five elements of SPARK: Storytelling, Purpose, Action, Relationships, and Kudos. Knowing how to tell a well-structured story is key to building long-term memory. Stating a clear purpose that doesn't take away from the discovery learning process is critical. Ensuring that people move from theory to practical application is imperative. Creating strong social learning is the key to commitment and engagement. Validating and affirming participants' comments is the way to create a positive learning environment.
Cracking the Workplace Discipline Code Main.pptxWorkforce Group
Cultivating and maintaining discipline within teams is a critical differentiator for successful organisations.
Forward-thinking leaders and business managers understand the impact that discipline has on organisational success. A disciplined workforce operates with clarity, focus, and a shared understanding of expectations, ultimately driving better results, optimising productivity, and facilitating seamless collaboration.
Although discipline is not a one-size-fits-all approach, it can help create a work environment that encourages personal growth and accountability rather than solely relying on punitive measures.
In this deck, you will learn the significance of workplace discipline for organisational success. You’ll also learn
• Four (4) workplace discipline methods you should consider
• The best and most practical approach to implementing workplace discipline.
• Three (3) key tips to maintain a disciplined workplace.
Attending a job Interview for B1 and B2 Englsih learnersErika906060
It is a sample of an interview for a business english class for pre-intermediate and intermediate english students with emphasis on the speking ability.
What are the main advantages of using HR recruiter services.pdfHumanResourceDimensi1
HR recruiter services offer top talents to companies according to their specific needs. They handle all recruitment tasks from job posting to onboarding and help companies concentrate on their business growth. With their expertise and years of experience, they streamline the hiring process and save time and resources for the company.
[Note: This is a partial preview. To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations]
Sustainability has become an increasingly critical topic as the world recognizes the need to protect our planet and its resources for future generations. Sustainability means meeting our current needs without compromising the ability of future generations to meet theirs. It involves long-term planning and consideration of the consequences of our actions. The goal is to create strategies that ensure the long-term viability of People, Planet, and Profit.
Leading companies such as Nike, Toyota, and Siemens are prioritizing sustainable innovation in their business models, setting an example for others to follow. In this Sustainability training presentation, you will learn key concepts, principles, and practices of sustainability applicable across industries. This training aims to create awareness and educate employees, senior executives, consultants, and other key stakeholders, including investors, policymakers, and supply chain partners, on the importance and implementation of sustainability.
LEARNING OBJECTIVES
1. Develop a comprehensive understanding of the fundamental principles and concepts that form the foundation of sustainability within corporate environments.
2. Explore the sustainability implementation model, focusing on effective measures and reporting strategies to track and communicate sustainability efforts.
3. Identify and define best practices and critical success factors essential for achieving sustainability goals within organizations.
CONTENTS
1. Introduction and Key Concepts of Sustainability
2. Principles and Practices of Sustainability
3. Measures and Reporting in Sustainability
4. Sustainability Implementation & Best Practices
To download the complete presentation, visit: https://www.oeconsulting.com.sg/training-presentations
Business Valuation Principles for EntrepreneursBen Wann
This insightful presentation is designed to equip entrepreneurs with the essential knowledge and tools needed to accurately value their businesses. Understanding business valuation is crucial for making informed decisions, whether you're seeking investment, planning to sell, or simply want to gauge your company's worth.
The world of search engine optimization (SEO) is buzzing with discussions after Google confirmed that around 2,500 leaked internal documents related to its Search feature are indeed authentic. The revelation has sparked significant concerns within the SEO community. The leaked documents were initially reported by SEO experts Rand Fishkin and Mike King, igniting widespread analysis and discourse. For More Info:- https://news.arihantwebtech.com/search-disrupted-googles-leaked-documents-rock-the-seo-world/
What is the TDS Return Filing Due Date for FY 2024-25.pdfseoforlegalpillers
It is crucial for the taxpayers to understand about the TDS Return Filing Due Date, so that they can fulfill your TDS obligations efficiently. Taxpayers can avoid penalties by sticking to the deadlines and by accurate filing of TDS. Timely filing of TDS will make sure about the availability of tax credits. You can also seek the professional guidance of experts like Legal Pillers for timely filing of the TDS Return.
Improving profitability for small businessBen Wann
In this comprehensive presentation, we will explore strategies and practical tips for enhancing profitability in small businesses. Tailored to meet the unique challenges faced by small enterprises, this session covers various aspects that directly impact the bottom line. Attendees will learn how to optimize operational efficiency, manage expenses, and increase revenue through innovative marketing and customer engagement techniques.
Affordable Stationery Printing Services in Jaipur | Navpack n PrintNavpack & Print
Looking for professional printing services in Jaipur? Navpack n Print offers high-quality and affordable stationery printing for all your business needs. Stand out with custom stationery designs and fast turnaround times. Contact us today for a quote!
Enterprise Excellence is Inclusive Excellence.pdfKaiNexus
Enterprise excellence and inclusive excellence are closely linked, and real-world challenges have shown that both are essential to the success of any organization. To achieve enterprise excellence, organizations must focus on improving their operations and processes while creating an inclusive environment that engages everyone. In this interactive session, the facilitator will highlight commonly established business practices and how they limit our ability to engage everyone every day. More importantly, though, participants will likely gain increased awareness of what we can do differently to maximize enterprise excellence through deliberate inclusion.
What is Enterprise Excellence?
Enterprise Excellence is a holistic approach that's aimed at achieving world-class performance across all aspects of the organization.
What might I learn?
A way to engage all in creating Inclusive Excellence. Lessons from the US military and their parallels to the story of Harry Potter. How belt systems and CI teams can destroy inclusive practices. How leadership language invites people to the party. There are three things leaders can do to engage everyone every day: maximizing psychological safety to create environments where folks learn, contribute, and challenge the status quo.
Who might benefit? Anyone and everyone leading folks from the shop floor to top floor.
Dr. William Harvey is a seasoned Operations Leader with extensive experience in chemical processing, manufacturing, and operations management. At Michelman, he currently oversees multiple sites, leading teams in strategic planning and coaching/practicing continuous improvement. William is set to start his eighth year of teaching at the University of Cincinnati where he teaches marketing, finance, and management. William holds various certifications in change management, quality, leadership, operational excellence, team building, and DiSC, among others.
3.0 Project 2_ Developing My Brand Identity Kit.pptxtanyjahb
A personal brand exploration presentation summarizes an individual's unique qualities and goals, covering strengths, values, passions, and target audience. It helps individuals understand what makes them stand out, their desired image, and how they aim to achieve it.
1. Managing UA projects
Setting expectations
through the Doc Plan
Larry Kunz
October 28, 2014 #writersua #techcomm
2. What we’ll cover today
Oct 28, 2014
@larry_kunz
• What’s a Doc Plan?
• Why a Doc Plan?
• Outline of the Doc Plan
• Dos and Don’ts
3. Who Is the Project Manager?
Oct 28, 2014
@larry_kunz
4. Oct 28, 2014
@larry_kunz
What’s a Doc Plan?
• Describes the design for the UA
(and other documentation as well)
• Describes the work needed to
develop the UA
• Defines the project’s scope
• Spells out every stakeholder’s
responsibilities
• Sets expectations
5. Oct 28, 2014
@larry_kunz
What’s a Doc Plan?
A “very necessary evil”
Alan Pringle & Sarah O’Keefe
Technical Writing 101
6. Oct 28, 2014
@larry_kunz
Why a Doc Plan?
• Get everyone’s understanding
• Get everyone’s buy-in
• Spell out assumptions /
contingencies
The Doc Plan functions
as a contract
Image: Ralph F. Stitt [Public domain], via Wikimedia Commons
7. The Doc Plan outline
Oct 28, 2014
@larry_kunz
• Product description
• Audience
• Documentation products
UA
design }
8. The Doc Plan outline
Oct 28, 2014
@larry_kunz
• Product description
• Audience
• Documentation products
• Work to be performed (tasks)
• Contingencies
(dependencies, receivables)
• Assumptions
• Budget
• Schedule
} UA
design
} Work
plan
9. Oct 28, 2014
@larry_kunz
Product description
• Not just the UA – but the product of
which the UA is a part
• What does it do?
• What customer “pains” is it designed
to address?
Purpose
• Validate my assumptions about
audience and objectives
10. Oct 28, 2014
@larry_kunz
Audience statement
• Who’ll use the UA?
– Background
– Objectives
– Prior knowledge, etc.
• In what situations will they use it?
Purpose
• Validate the design of the UA
11. Documentation products
• Description of all documentation,
including the UA
Oct 28, 2014
@larry_kunz
– Media
– Audience
– Tasks supported
• Description of how requirements are
being satisfied (or not)
Purpose
• Put the UA in context – as part of the
overall UX
• Validate the project’s scope
12. Oct 28, 2014
@larry_kunz
Tasks (work items)
• Major units of work the UA team will
perform – for example:
– Design & develop tooltip help for
Configuration Manager
– Update HTML help system for Operator
Console
• Estimated effort for each major unit
Purpose
• Verify that all requirements are being
addressed
• Validate assumptions about estimates
13. Oct 28, 2014
@larry_kunz
Contingencies
Scope (Baseline) If your project is to succeed….
• What really has to go right?
• What do you need, and when?
• Whose help do you need?
• What schedule checkpoints depend
on other stakeholders?
Purpose
• Make all dependencies clear
14. Oct 28, 2014
@larry_kunz
Assumptions
• The rules of the road, for example:
– The tools we’ll use
– The style guide we’ll use
– Our process for draft reviews
– How we’ll integrate the UA with product
builds
Purpose
• Inform other stakeholders
• Inform the UA team
15. Oct 28, 2014
@larry_kunz
Budget
• How much I plan to spend on each
major part of the project
Purpose
• Secure necessary approvals
• Form a basis for tracking
the project
(along with schedule)
16. Oct 28, 2014
@larry_kunz
Schedule
• How much time my team needs for
each major task (work item)
• Checkpoints – for example:
– When the first draft will be review ready
– When everything will be translated
Purpose
• Validate other stakeholders’
dependencies on me
• (Again) form a basis for
tracking the project
17. The Doc Plan Outline
Tooltip help will
Oct 28, 2014
@larry_kunz
• Product description
• Audience
• Documentation products
• Work to be performed (tasks)
• Contingencies
(dependencies, receivables)
• Assumptions
• Budget
• Schedule
be written
using Javascript
18. The Doc Plan Outline
Tooltip help will
Oct 28, 2014
@larry_kunz
• Product description
• Audience
• Documentation products
• Work to be performed (tasks)
• Contingencies
(dependencies, receivables)
• Assumptions
• Budget
• Schedule
be written
using Javascript
19. The Doc Plan Outline
50 Tooltip help
strings will
require 24
writer-hours
Oct 28, 2014
@larry_kunz
• Product description
• Audience
• Documentation products
• Work to be performed (tasks)
• Contingencies
(dependencies, receivables)
• Assumptions
• Budget
• Schedule
20. The Doc Plan Outline
50 Tooltip help
strings will
require 24
writer-hours
Oct 28, 2014
@larry_kunz
• Product description
• Audience
• Documentation products
• Work to be performed (tasks)
• Contingencies
(dependencies, receivables)
• Assumptions
• Budget
• Schedule
21. The Doc Plan Outline
Writers will
have a product
prototype to
work with
Oct 28, 2014
@larry_kunz
• Product description
• Audience
• Documentation products
• Work to be performed (tasks)
• Contingencies
(dependencies, receivables)
• Assumptions
• Budget
• Schedule
22. The Doc Plan Outline
Writers will
have a product
prototype to
work with
Oct 28, 2014
@larry_kunz
• Product description
• Audience
• Documentation products
• Work to be performed (tasks)
• Contingencies
(dependencies, receivables)
• Assumptions
• Budget
• Schedule
23. Oct 28, 2014
@larry_kunz
Do….
• Include all relevant content
– When in doubt, put it in
– But don’t include content just
to fit some “template”
• Leave as little to chance as
possible
• Refer back to the Doc Plan
as the project moves along
24. Oct 28, 2014
@larry_kunz
Don’t….
• Skip the doc plan (or parts of it)
• Assume that someone has all the
answers
• Tolerate scope creep
25. Oct 28, 2014
@larry_kunz
The Doc Plan…
• Defines the project’s scope
• Functions as a contract between you
and other stakeholders
• Provides a road map for the UA team
• Serves as a basis for tracking the
project
27. Oct 28, 2014
@larry_kunz
Stay in Touch!
Larry Kunz
Twitter: @larry_kunz
larrykunz.wordpress.com
lk81924@gmail.com
Editor's Notes
A marriage – a friendship – any human endeavor…
…Only works when everyone shares the same set of expectations
Back in the day, we watched Ed Sullivan on Sundays
This is what passed for entertainment
The person on the right is pointing to the plates that need attention
You’re the guy on the left, running around responding to the needs and keeping all the plates spinning
The doc plan sets expectations
Makes the plates spin better
Keeps anyone from introducing new plates, unexpectedly
The doc plan, also known as the project plan for the UA team
For now, here’s a summary of the doc plan and why it matters
This document, simply, describes:
The design for the information (description of the deliverables)
The work that will go into making the deliverables (the project plan)
Spells out the responsibilities of everyone on the projectEveryone = your team AND the other stakeholderse.g., “SMEs will provide reviews of docs between March 1 and 15”
Your assumptions about the project are correct
Creating a Doc Plan – and getting it reviewed and approved – might seem hard
So hard, it’s not worth the bother
Resist the temptation to bypass the doc plan and just start writing
Pringle & O’Keefe call the doc plan a “very necessary evil”
Wouldn’t it be easier to just start developing the UA and let the chips fall where they may?
No – the Doc Plan is necessary
It sets expectations
It makes clear what your team needs
It helps defuse conflicts later on
As the Marx Brothers said: Why a Duck?
Or Why a Doc Plan?
The doc plan is your chance to make sure that:
Everyone understands who’s doing whatEveryone = your team AND the other stakeholderse.g., “SMEs will provide reviews of docs between March 1 and 15”
Your assumptions about the project are correct
And another reason the doc plan is important:
It’s a contract between you and the other stakeholders
As you manage the project, you need to be certain that:
Your team members have everything they need
Your team is delivering everything that’s expected of it
You’re not going to be blamed if (when) things go wrong
This “contract” will help ensure that those things happen
Time and again I find that you can’t assume anything
Even when you think that something is obvious to everyone…
….It usually turns out that it was obvious to no one but you
Later we’ll cover all the various things you’ll need to put in the doc plan
We want to validate our assumptions so that there are no surprises later
That’s a common theme throughout the doc plan
Now specifically describe the UA, not the product
Also describe other documentation the end user will have access to
….So that the UA is couched in the context of the entire User Experience
Also, enumerate the project requirements
Define which ones are being met, and which ones are not
“Requirements met” defines the project’s scope
(Requirements not met are exclusions)
This is the part of the Doc Plan where all requirements should be reflected…
….Even if only to identify some of them as exclusions (i.e., outside the scope)
In this way, the whole project team has to buy off on your vision of the project’s scope
Now we turn the corner
From describing the UA and how it’s used
To describing the internal processes and the work that goes into it
Let’s do an exercise to see if you know where certain items would go
This a description of the documentation (which includes the UA)
It’s not a description of the product – that would be about the software itself
It’s not an estimate of hours – just a statement of what’s included
Second item in the exercise
This is a description and sizing of the work to perform
It’s not budget (which will include this, converted to dollars and rolled up with other items)
It’s not schedule: it doesn’t show where this task fits into the overall plan
Third item in the exercise
Let’s do an exercise to see if you know where certain items would go
(I wouldn’t mark you wrong if you said Assumptions)
Best practices
Include all relevant content
If you’re not sure whether to include it, then include it
OTOH every project is different
Your doc plan won’t look exactly like my doc plan
Don’t be a slave to some kind of template (even if it’s my template)
Leave as little to chance as possible
Don’t assume other stakeholders will be on board, unless it’s in writing
Keep referring back to the Doc Plan as the project moves along
The Doc Plan is the road map for the project team
It tells them what to do, when, and how
And as you manage the project, it helps you….
Remind other stakeholders of your requirements / contingencies
Keep the work scope clear
Resolve disputes
Track the project against budgets & schedules
Best practices / converse
Don’t skip doing the doc plan (or parts of it)
It might seem like an evil, but it’s a “very necessary evil”
Without it, your project will go awry, expectations will go unmet, and conflict will occur
Don’t assume that someone has all the answers
Often, your doc plan will prompt questions –
Like “Who is responsible for providing the software prototypes” –
That no one has thought of, until you asked the question
What happens then? Maybe you get to recommend the answer
Don’t tolerate scope creep
It’s easy to say, “Sure, we’ll help out with that”
But remember to be loyal to your team: don’t saddle them with extra work
Summary
The Doc Plan:
Defines the project’s scope
Functions as a contract between you and other stakeholders
Provides a road map for the UA team
Serves as a basis for tracking the project
Bottom line: it sets expectations equally, for the UA team and for all stakeholders