Jeanette Evans: Links//videos/white papers

Links//videos/white papers

Sample links

Emerging technologies in higher education (video created for Cuyahoga Community College, for National Distance Learning Week)
http://oxygen.tri-c.edu/podcast/jevans/Emerg_tech_fri_-_Web_(1024x768)_-_20121012_10.03.50AM.html

Storyboarding in Instructional Design Applications - (video created for Cuyahoga Community College, for National Distance Learning week) http://breeze.tri-c.edu/storyboardingl/
Lines and Letters - NEO STC newsletter (co-editor, contributor)
Tri-C Title III - informational blog (contributor)
FOEC News - Friends of Euclid Creek newsletter, (editor)
What We Can Learn from Project Managers, Intercom, Society for Technical Communication, ArlingtonVA, February 2011 (with Sandy Moses). Available for those with user name and password to stc.org at http://intercom.stc.org/2011/02/what-we-can-learn-from-project-managers/

White Papers: Support Adoption of Technology and Initiatives

https://docs.google.com/file/d/0ByOFUxM0iUondzZUdVdQVjk2OHc/edit?usp=sharing

Open Educational Resources

https://docs.google.com/file/d/0ByOFUxM0iUonMXBNUlpJWUttUWs/edit?usp=sharing

Project Management: Steps that Lead to Project Success

https://docs.google.com/file/d/0ByOFUxM0iUonaDNLRmVvbC1SR0U/edit?usp=sharing

Storyboards: Applications in Academic and Instructional Design Environments

https://docs.google.com/file/d/0ByOFUxM0iUonZjBLbDlJQzFqcHM/edit?usp=sharing

THOUGHTS ON WHITE PAPERS (EXCERPT, LINES AND LETTERS, newsletter of the neostc)

Ways to get started

Here are some questions to answer to get started in writing a white paper.

Why should someone read this white paper?
What is the message of the white paper?
Who are the target readers?

White Paper Boot Camp at http://www.whitepaperbootcamp.com/
provides ideas about how to approach writing with a 10-step process. Here are the first five steps.

Clarify the topic.
Identify the ideal reader.
Decide on an objective.
Develop an outline.
Interview the experts.

Write as a team: pros and cons

Advantages and disadvantages exist when it comes to writing as a team.

Disadvantages include that the process can:

take more time than individual writing
lead to interpersonal conflict
yield a disjointed document and inequitable workloads
lead to thinking that promotes conformity and make an inferior document because no one wants to ask tough questions

Advantages include that the process:

draws on a greater knowledge base
benefits from a greater skills base
can provide a better idea of how the audience will read the document

The primary author of the white paper should weigh the pros and cons and decide what is best (pros and cons adapted from Markel, Technical Communication, St. Martin’s Press).

No comments:

About me

Writer, editor, communicator, instructor, and consultant/analyst with a broad base of experience and skill in instructions, procedures, manuals, web design, HTML, on-line help, documentation, business communications, blogging, articles, medical/scientific/technical manuscripts, grant writing, and standards development. Able to deliver workshops and instructional courses on a variety of topics. Over 10 years in a medical imaging environment as well as contract/freelance/consulting work with a wide range of clients.

What We Can Learn From Project Managers (excerpt)

By Jeanette Evans and Sandy Moses

Classic project management techniques can add to the success of projects and initiatives. We can learn much from these techniques and processes as we think about applying them to a range of projects such as adoption of a content management system, development of a set of documents, or release of a new help system. Here are some of the ideas we cover in this article:

Start with the project sponsor and approved project charter
Identify critical elements to the project charter
Remember to manage by objective
Use a project plan
Remember inclusion and the perspective of others
Understand the project process that includes initiate, plan, execute, monitor and control, and close

The Project Sponsor and Approved Charter

In most settings, success of a project is related to sponsor buy-in. The sponsor will act as your project champion, and without the support of a sponsor, people will not see value in your project. The sponsor is the visionary, and when you have roadblocks, which you mostly likely will, the project sponsor can guide you through the traffic and open the lane for you to go through. Once you have a sponsor, develop a project charter to get official approval for the project.

In developing the project charter, follow these guidelines to maximize your chances for success:

Identify the project stakeholders. Typically these are the executives of the departments the project will impact.
Form the project steering committee from the project stakeholders. These are the leaders in the areas that will be impacted by the project.
Contact the stakeholders to ask for their approval and to add members of their departments to the planning and implementation team.

Critical elements in working with the project charter include the following:

Ask the stakeholders to name and approve the project planning and implementation team members, who are usually their direct reports. In most businesses and academic institutions, the management style is mostly hierarchical, or top down, and if you ask for the input of executives as you build your team, you will have much more stakeholder and team buy-in.
Allow the project planning and implementation team members to have a say in defining the roles they will play on the team, since the charter is a contract between the team and the steering committee.
Provide some preliminary budget information when you present your project charter, to show what the project will cost and how it will be funded.
Identify a target project timeline with some milestones.

The most important part of the project charter is the scope statement. A well-defined statement of what is in scope and what is out of scope will keep the project focused, help prevent scope creep, and set appropriate and realistic expectations for the project stakeholders and sponsor.

One thing that can keep a project from being completed on time is scope creep. An agreed-upon, focused scope statement in the approved project charter and a realistic timeline should lead to a successful project. Remember, the project charter is a contract between the project team and the steering committee.

How does one define a successful project? The triple constraint as shown in the Project Management Triangle applies.

The product deliverable meets the elements of the project scope.
The project scope is well defined.
The project is on time and within budget.

Management by Objective

Here are some guidelines on how to manage by objective,
a concept that will help make your outcome successful.

Establish clear and realistic objectives to develop your scope statement. SMART—Specific, Measureable, Attainable, Realistic, Timely—objectives should apply here.
Periodically evaluate whether objectives are being met. The project manager should provide an executive summary to the project sponsor and project team biweekly or monthly, and more often closer to the launch of the project. On larger projects, the team should meet weekly before launch, always referring back to the project plan.
Implement corrective action when a problem arises.

Project Plan

Some steps in the process of using a project plan are:

The project manager sets up a preliminary project plan and schedule with high-level milestones.
The plan reflects the organization’s work calendar—for example, the fiscal year, holidays, closings.
The preliminary project plan is presented to the planning and implementation team.
Once the milestones are approved by the team, the project manager and the project team create the detailed project plan of tasks that make up the project milestones (the work breakdown structure).
Team members treat the project plan as a living document that will change as more information becomes available and more tasks are outlined. The milestones, however, should not move too much, only within the slack built into the project plan, or the deadlines will slip.

Inclusion

In both corporate and academic settings, it is important to be collegial and include all parties that would be impacted by the results of the project. The most successful projects are those where the work includes the perspectives of everyone who might touch the project or use the deliverable. A project is worthless if the end users of the product or service choose not to use it because the deliverable does not suit their needs.

Project Process

Here are the steps in classic project management as we use them, as adapted from the PMBOK Guide. Use these proven methods to maximize the chances that your project will succeed.

Initiate

Select a project manager
Divide large projects into phases
Determine project objectives
Document assumptions and constraints
Develop project charter
Develop preliminary project scope statement

Plan

Create project scope statement
Determine team
Create work breakdown structure (WBS)
Create activity list
Estimate resource requirements
Determine metrics
Estimate time and cost
Develop schedule
Determine roles and responsibility
Identify risk
Prepare procurement documents
Gain formal approval

Execute

Finalize team
Execute plan
Recommend changes and corrective action
Follow processes
Conduct team building
Schedule progress meetings
Select sellers (vendors)

Monitor and Control

Assess team against performance measurement baselines
Measure according to project plan
Determine variance and need for corrective action
Verify scope and check for scope creep
Integrate change control
Perform risk audits
Manage reserves
Use issue logs
Facilitate conflict resolution
Measure team member performance
Report on performance
Create forecasts
Administer contracts

Close

Develop closure procedures
Complete contract closures
Confirm work was completed per requirements
Gain formal acceptance of product
Provide a project “post-mortem”
Complete final performance reporting
Index and archive records
Update “lessons learned” knowledge base
Hand off completed product
Release resources

SANDY MOSES (sandymmoses@gmail.com) is the manager of online support services in the Office of eLearning and Innovation at Cuyahoga Community College. She has an MSM in information systems in business and more than 10 years’ experience in corporate and higher education. While earning her MA degree, she worked in distance learning at The University of Akron. At Case Western Reserve University, she managed an online educational program for the Center for Science and Math Education. She has also taught part-time as an assistant lecturer in business technology. Sandy has more than 107 contact hours in project management education and more than seven years of project management experience, recently earning her Project Management Professional (PMP) certification from the Project Management Institute.

JEANETTE EVANS (jeanette.evans@sbcglobal.net) has been involved in communication work for more than 15 years in both academic and corporate environments. She received her MS in technical communication management from Mercer University. In addition to her work experience, Jeanette taught technical communication at Cuyahoga Community College in a technical communication certification program, is a frequent contributor to Intercom, and provides book reviews for Technical Communication. She is an STC Associate Fellow and active in the Northeast Ohio STC community, currently serving as co-editor of Lines and Letters.

References

PMBOK Guide, 3rd ed. Newton Square, PA: Project Management Institute.

Pages

Links//videos/white papers

THOUGHTS ON WHITE PAPERS (EXCERPT, LINES AND LETTERS, newsletter of the neostc)

No comments:

Post a Comment