INTE 5160 Summer 2014 Project Management Knowledgebase ...€¦ · INTE 5160 Summer 2014 Project...

INTE 5160 Summer 2014 Project Management Knowledgebase Diigo Group ______________________________________________________________________________________

Scope Statement

Background/Context Finding and sharing information on the Internet is a valuable resource for all students. While incredibly valuable, the magnitude of resources can easily become overwhelming. Mitchell Kapor, personal computing pioneer has said, “Getting information off the Internet is like taking a drink from a fire hydrant.” Many solutions now exist to make that “fire hydrant” more manageable. Since 2011, the instructor and students in INTE 5160: Managing Information and Learning Technology Programs has utilized Diigo as its knowledgebase solution for managing the resources curated by the students and staff of this class. Diigo’s simple, intuitive and collaborative functionality made adding information easy and useful for students. The Project Management Knowledgebase Diigo Group now houses more than 900 resources that students have compiled over the past five semesters. The Diigo site used for the ILT Program has now become as unwieldy as a fire hydrant in searching for and selecting information.

Since 2011, the instructor and students of INTE 5160: Managing Information and Learning Technology Programs at UC Denver, have been collaborating on a knowledge base for the curation of project management resources. Diigo, a social bookmarking tool, was chosen as the tool to archive these resources because of its intuitive interface and collaborative functionality. The Diigo platform will continue to be used to add to the collection of resources, but a new site would provide a more effective and efficient interface from which to access the curated collection.

Problem Statement While Diigo continues to be a great solution for collaborative curation of project management articles, it lacks the organization that would allow users to quickly and efficiently find specific types of information to accommodate the growing number of resources. In addition, there are numerous duplicate entries and broken links. Previous, present, and past students – as well as the general public interested in project management – have difficulty searching, organizing, or navigating to information that is pertinent to their specific need (s). This could cause user frustration.

Audience Analysis The target audience includes past, present and future students and faculty within the University of Colorado Denver ILT (Instructional Learning and Technologies) program. The members of this audience are looking for the ability to curate, organize and share project management resources.

The secondary audience may also include the following:

Public internet users who are looking for information regarding project management, which could include other educators, instructional designers and educational technologists.

A variety of organizations including education, corporate settings, government, and nonprofit agencies.

1


We propose a brief survey of the audience to better establish their needs. This is described in the scope of work. It’s important to point out that users outside of the UC Denver ILT program will be able to access the materials on the Project Management Knowledgebase, but they will not be able to curate.

Proposed Solution / Statement of Work Prior to any work beginning, we believe additional audience analysis is needed. This will be done to fully understand the needs and requirements of our primary and secondary audience. To do this we will:

Create a brief survey to gather information from the existing Diigo group members (representing past and present students in INTE 5160). The survey will assist us as we attempt to gather information on the sites purpose and functionality.

Using the same survey, identify students in the INTE program who have not yet taken the course to send the survey too. This will require collaboration with the University of Colorado to determine the best way to reach this group.

Gather information from the general public through the use of social media groups (Facebook or LinkedIn groups of people interested in Instructional Design, Development and Project Management) to solicit input on resource needs and to determine the methods currently being used to locate resources. In addition, we would request information about what is working and/or not working when searching for resources.

We believe the best approach to finding the most successful solution will be to conduct a pilot study and evaluate the three different sites which might be used to access the resources on Diigo. We recommend the following approach:

1. Prepare an evaluation and scoring sheet using the sponsor’s requirements and audience needs

analysis survey. Determine minimum mandatory requirements. 2. Evaluate and rank the following options: WordPress, Wikispaces Classroom and Google Sites. Eliminate

any of the options that do not meet mandatory minimum requirements. 3. Setup a functional website mockup for each option containing two pages of sample curated items. 4. Evaluate the usability, flexibility, maintainability and search engine optimization potential of each solution,

and seek input from the sponsor on the final selection.

We believe this approach will lead to the best outcome and minimize the risk of choosing an inferior solution that could lead to disappointment and another migration attempt. We’ve included search engine optimization above because we believe it will be important for the site to rank high in search engines, making it easier for the public members of our audience to find it (DeMers, 2014).

We propose that three teams each work independently to evaluate the following three options: Wordpress, Wikispaces Classroom and Google Sites. Rather than to simply transfer the resources hosted on Diigo to another platform, we propose finding a solution which will transform access to the resources of Diigo, as the Diigo platform may still serve as an important ongoing resource. The first option, WordPress, provides a solution for allowing a website to use a Diigo RSS feed

2

INTE 5160 Summer 2014 Project Management Knowledgebase Diigo Group ______________________________________________________________________________________ composed of an individual tag or a combination of tags. This feed would then be used to display the links for a specific topic in a web page. Curation software typically has the ability to use a data source such as an RSS feed. One of the advantages of utilizing this is that the same link may fit into several categories and it can be displayed in multiple web pages if there are multiple tags. This makes maintenance easier, as a broken link only has to be repaired on Diigo once and not in three web pages on the project management website. There are several curation plugins available for WordPress. We’ll investigate free hosting options for WordPress including the possibility of hosting it on one the UC Denver’s web servers.

A second option is to use Wikispaces Classroom as the end user solution to provide a onestop resource for information regarding Project Management. As with the proposed WordPress solution, this option would continue to use the Diigo platform as the primary collection tool. Wikispaces Classroom was selected for evaluation for the following reasons: it’s userfriendly, collaborative, it provides flexible organization and editing tools, it supports mobile platforms and it’s free.

The third option involves restructuring the current resources within Diigo, and then accessing these resources through a Google Site. This Google Site would work as a complement to the existing Diigo site. There are several features that we believe make Google Sites worth evaluating. The List Pages and File Cabinet features will allow for the storage and organization of content and information. The Announcements feature provides space and the ability to have blogtype conversations around relevant topics. The goals and the tools that define this solution can add a level of structure, reliability, ease, accessibility, and community to the Managing Information and Technology Programs’ space.

We propose that regardless of the solution chosen, we work with the sponsor to:

1. Develop curation guidelines for contributors to include a preselected set of tags. 2. Perform a quality check on the Diigo data and edit existing tags where needed to fit the curation tag list. 3. Remove duplicate links. 4. Use a link checking tool to find broken links and then repair or remove them. 5. Recommend topics for the website pages to the sponsor based on the tags in Diigo.

We believe that our approach will provide the best solution for our audience and will transform the resources available into a userfriendly, structured environment which facilitates ease of maintenance.

Requirements

The following requirements have been identified by the project sponsor:

The proposed solution should be a site with a well defined information architecture that supports an intuitive experience for end users.

The proposed solution should be publicly accessible to anyone interested in program management. The proposed site should be able to organize resources by topic, categories, live links, and should retain

Diigo’s comments. The proposed solution should also allow for correct plugins, tagging, commentary about resources, a

rating system, and greater ease of locating resources.

3


The proposed site should also have the ability to add resources as the Diigo collaborative knowledge base grows.

The proposed site should be free to both the instructor and end users.

Constraints Eight constraints have been taken into consideration in providing the recommendation of a solution, the creation of a milestones timeline, and in establishing parameters for the new sites’ functions.

1. Students who will be working on the project are subject to time limitations, often juggling school work with other professional and personal commitments.

2. The instructor’s time is also limited, so the solution must be able to be implemented with little followup and/or upkeep from the faculty member.

3. The project will be developed by students within the ILT program, many of whom are located across a large geographic area. Students will be communicating through cellular and internet collaboration technologies (e.g., webconferencing).

4. The total time given to complete the project is limited to 46 weeks. 5. The survey will need to take place in a short amount of time thus limiting the number of responses. 6. There is no budget for project, requiring students to use free tools and to volunteer time to complete the

project. 7. Expertise on the use of the tools is limited to the students on the development team and development

time may take longer to accommodate the learning curve. 8. The project sponsor will need to choose between the three sites based on the ranking sheet and review

of the three prototypes within a short amount of time.

Assumptions The team has made the following assumptions regarding the scope of work:

The new solution will not transfer or replace the resources within Diigo. Instead, it will improve curation and access to the resources residing within Diigo.

The new solution will allow for quick access to the resources within Diigo and that Diigo will continue to remain a free and accessible site.

A free and acceptable website solution exists. The class that will complete the project will have enough students and the skills needed to carry out the

work in building the knowledge base. Ongoing maintenance of this resource will be managed by Kenny Hirschmann & future students in INTE

5160. Funds will not be available in the future so the site should maintain its free status.

Exclusions The following list of items are beyond the scope of this project. If these items are desired, a new proposal will need to be submitted and approved.

4


Ongoing maintenance of the new site Plans for future development Vetting of resources limited to current status The inclusion and editing of media or the conversion of media resources to other formats (e.g., Flash to

HTML5) Editing user input for grammar, typographical errors, or correctness Training or support for the end user and therefore must be intuitive in nature to support the ease of the

user

Stakeholders The stakeholders of this project are:

The project sponsor and current instructor of INTE 5160 at UC Denver Kenny Hirshman Current, past, and future students in the ILT program at UC Denver Instructors in the ILT program at UC Denver The UC Denver IT Department Project Management Professionals Educators, instructional designers, educational technologists, and other internet users who are looking

for resources related to project management

Milestones

Project Milestones Due Dates

Project Start: Convene Team and Establish Regular Check In Times, Confirm Roles

and Work Assignments and Confirm Timelines. Develop and Distribute Audience Analysis Survey Initiate Diigo Analysis

August 01, 2014

Analyze Audience Analysis Survey August 15, 2014

Develop Curation Guidelines and Website Categories August 18, 2011

Sponsor SignOff on Diigo Revisions/Guidelines Document August 26, 2014

Begin Website Evaluations using Scoring Sheet Sept. 6, 2014

Design and Develop Prototype/MockUps of sites that meet the requirements. Sept. 6, 2014

Deliver Prototypes and Scoring sheet to Project Sponsor for Review Sept. 10, 2014

Project Sponsor Signs Off on and Selects a Prototype Sept. 12, 2014

Begin Development of New Project Management Site Sept. 16, 2014

5


Diigo Revisions Complete Sept. 18, 2014

Sponsor SignOff on Diigo Revisions Sept. 18, 2014

Project Management Site Complete & Ready for Review Sept. 19, 2014

Project Sponsor will Review the Site and either Approve or Make Recommendations for Improvement.

Sept. 22, 2014

Revisions (if needed) are Ready for Sponsor Review Sept. 24, 2014

Project Sponsor Acceptance and SignOff Oct. 6, 2014

Launch final website Oct. 8 2014

Resource Plan

Staffing Due to the constraints of little or no budget, project staff will have to volunteer their time. The staffing plan for this project will consist of current and future students enrolled in the INTE 5160 course. Future students will be volunteering based on the amount of hours required to participate in the course, which will be limited to approximately 810 hours per week. This means that on top of other course responsibilities, student volunteers are likely to work 24 hours a week on this project specifically. (Note that in the activity plan specific individuals from the teams below have been assigned to activities. For example the developer with expertise on Wordpress would be assigned to those activities.)

Roles Responsibilities

Project Team (Current Students)

This team will scope and plan the project’s initiation stage, strategy stage, analysis stage, design and build stage, and implementation stage.

Project Sponsor This individual (Kenny Hirschmann) will have the decisionmaking authority for which hosting/authoring tool will be used to build the site. This individual will communicate the business goal to the team and monitor throughout development to make certain that the project’s features adhere to the business goal. This individual will also communicate project status to any stakeholders that are not part of the project team.

Project Manager This individual will report to the Project Sponsor. This individual will plan and organize the execution of the project’s actions, everything from scope to implementation. This individual will communicate milestones and deadlines to the teams listed below. This individual will lead the entire team and help keep the

6


project in motion at all times. The project manager will need to be proficient in the following areas: 1) Identifying potential roadblocks related to budgets, resources and timelines, while reporting these potential issues and making modifications as needed. 2) Communicating on a regular basis each week with all team members regarding status and workflow. 3) Managing time to keep the team on task so that key deliverables will arrive on time. 4) Directing the team and keeping record of milestones and progress.

Web Analysts This team will analyze the entire context of the Diigo space. This will include analysis of the design features, the material, and the navigation options and requirements. Additionally, this team will compare their findings to those taken from the Audience Analysis surveys. Finally, this team will be responsible for going through each resource tag and curating all quality resources. These individuals, the web analysts, should have some experience or familiarity with web design and development. Team reports to project manager.

Designers This team will take the content from the analysis team and begin building design storyboards. Ultimately this team will be responsible for the look and feel of the interface of the site as well as choosing where the content lives on the site and how users can interact with it. Team reports to project manager.

Developers This team will work with the designers and web analysts to turn the conceptual design into a functional website using the chosen web hosting/authoring tool to build the information architecture. This team will attempt to troubleshoot any technical issues that exist between the conceptual design ideas and the actual product. Individuals on this team should have some background with HTML and CSS. Team reports to project manager. Included on this team are the Google Site Developer, Wikispaces Developer and WordPress Developer.

Quality Assurance Staff

This team will test the site and provide feedback to the development team, feedback around functionality, navigation, and spelling and grammar. This team will not provide feedback on design, as that has already been approved at this point. There will be a scorecard to guide this teams critique. Quality Assurance specialists will need to be proficient in the following areas: 1) Identifying and recognition of typos and a lack of clarity. 2) Communicating with team members regarding errors and suggestions for corrections. 3) Thinking abstractly in order to quickly solve issues. Team reports to project manager.

Communication Team The Communications team will communicate with all external contacts during survey and site promotion phase. This team will plan the site rollout, including putting together a campaign to advertise its quality and features to potential users. This team will also produce a survey to be given to users after the site is live for a certain period of time week. Team reports to project manager.

7


Work Breakdown Structure

8


Activity Analysis In the linked spreadsheet the activities, descriptions, dependencies, Staff, time and due dates are projected. Due to this project having no budget, no monetary cost estimates are shown. Staffing for this project will be provided by students in the INTE program. https://docs.google.com/spreadsheets/d/17ca9gWknSBHVjMWQRYaEdGPxmPec8MBuT5vbwNnB8Bc/edit?usp=sharing

Risk Management & Mitigation Matrix The matrix below identifies risks associated with this project, the probability of each risk occurring and the impact each risk will have on the project. The priority of each risk has been assessed and mitigation measures have been noted.

Risk Risk Description Probability Impact Priority Counter measures

Notes

001 Free hosting plan suitable for project needs is not available.

MEDIUM HIGH MEDIUM Contingency Google Sites and Wikispaces: If one of these ceases to be free, switch to the second best choice from the prototype evaluation. WordPress: Prior to project start, investigate possible funding of up to $100 a year to cover hosting costs through sponsor, ILT department or crowdfunding through ILT students and alumni.

002 Limited feedback is collected from the Audience Survey

MEDIUM MEDIUM MEDIUM Reduction/ Contingency

Reduction: Email and post links to the

survey on social media sites with appropriate instructions, encouraging completion. Reminder emails will be sent 2 days before survey deadline.

Contingency: If the response rate is low, then

the project sponsor will be given options based on team suggestions.

003 The site build takes longer than anticipated


One or more of the following will be used to mitigate the risk.

9

https://docs.google.com/spreadsheets/d/17ca9gWknSBHVjMWQRYaEdGPxmPec8MBuT5vbwNnB8Bc/edit?usp=sharing

https://docs.google.com/spreadsheets/d/17ca9gWknSBHVjMWQRYaEdGPxmPec8MBuT5vbwNnB8Bc/edit?usp=sharing


Reduction: Prior to project start, develop a

list of past class participants and ILT alum volunteers willing to assist in building the site. Add a team of volunteers to the build stage.

Contingencies: Offer extra credit to students

who put in extra hours to complete

Complete the project over two semesters

004 PressForward plugin development & supports is no longer available

LOW MEDIUM LOW Contingency Prior to project start, investigate and list one other suitable curation plugin as an alternative.

005 Lack of team member agreement on Diigo evaluation criteria

LOW LOW LOW Contingency Solicit feedback from project sponsor for resolution.

006 Insufficient student resources available to start or complete work

LOW HIGH MEDIUM Reduction/ Contingency

One or more of the following will be used to mitigate the risk. Reduction:

Prior to project start, develop a list of past class participants and ILT alum volunteers willing to assist in building the site. Add a team of volunteers to the build stage.

Contingencies: Offer extra credit to students

who put in extra hours to complete the project.

Complete project over two semesters

007 Loss of project manager or team members at a critical time

MEDIUM MEDIUM MEDIUM Contingency The project manager will keep the team informed of any challenges. Another student will serve as an assistant project manager in order to keep abreast of information and to step into

10


the role of PM if the project manager unexpectedly leaves either permanently, or for a short period of time. Project Manager will include alternates in project for emergencies and or additional volunteers to staff vacancies

008 Students lack experience in the skills needed to build the website


Prior to project start, develop a list of past class participants and ILT alum volunteers with needed skills willing to assist in building the site.

009 The analysis and revision of Diigo takes longer than expected

LOW MEDIUM MEDIUM Contingency Project manager will track progress against the time allotted for the analysis. If the team starts to get behind, the PM will hold a meeting and together the group will problem solve solutions to get back on track. If PM determines that additional help is needed, he/she will estimate the time needed to finish. Then, requests for help will be made from the volunteer list mentioned in risk 008 above or the sponsor will be asked to offer extra credit to students willing to work additional hours.

010 Project plan is not of satisfactory quality

LOW MEDIUM MEDIUM Contingency There are several checkpoints throughout the project plan, which allow for quality assurance and sponsor review. If a section does not meet quality standards, then the project sponsor will notify the PM who will call a team meeting to discuss and remedy the issues.

011 Use requirements change after project is underway

MEDIUM HIGH MEDIUM Contingency/ Reduce Meet with project sponsor weekly to

review timetables and deliverables. Assess likelihood of requirements changing with project sponsor

11


Risk Priorities We used the following scheme to prioritize our risks:

High Priority Risks: High Risk/High Impact Medium Priority Risks: High Risk/Low Impact, High Risk/Medium Impact, Medium Risk/High Impact,

Medium Risk/Medium Impact and Low Risk/High Impact Low Priority Risks: Medium Risk/Low Impact, Low Risk/Medium Impact and Low Risk/Low Impact

Probability Impact Grid

Probability

High

Medium 002 003 007 008

001 011

Low 005 004 009 010

006

Low Medium High

Impact

Rationale High Priority High priority may typically be defined by any risk that has both a high probability and a high impact. No risk is listed as High Priority. Medium Priority Medium priority is defined by any combination of High Risk/Low Impact, High Risk/Medium Impact, Medium Risk/High Impact, Medium Risk/Medium Impact and Low Risk/High Impact Risk 001: We have identified the risk associated with an inactive or unsupported authoring/hosting tool as

medium priority. The probability of this risk occurring is medium. The reason it is rated as medium is

12


because the eligible authoring/hosting tools are all popular and have already existed for several years. The impact of risk 001 is rated as high. The reason it is rated as medium is because there are a number of similar authoring/hosting tools that could be used in lieu of the “chosen” tool. This might mean a bit of replanning or retraining. For WordPress the risk of not finding a free hosting solution will be mitigated by locating potential funding before the project starts.

Risk 002: We have identified the risk associated with limited feedback as a medium priority. The reason that it

is rated as medium is because the possibility of people not responding to the survey could happen if a variety of avenues such as social media are not used. The probability of this happening is medium. If survey results come in lower than expected the PM will be given option by the team for additional revised surveys.

Risk 003: We have identified the risk associated with the site build taking longer than anticipated as a medium

priority. The probability of this risk occurring is medium. The reason for this is because it is not detrimental to the completion of the project, but could cause problems as the semester ends and tasks are left for a new class of students. A reduction strategy will be implemented prior to project start, a list will be developed of past class participants and ILT alum volunteers willing to assist in building the site, as well as add a team of volunteers to the build stage. A contingency plan will offer extra credit to students who put in extra hours to complete.

Risk 004: We have identified the risk associated with the PressForward plugin development ending as a low

priority. The impact is medium because it doesn’t nullify the choice of Wordpress just the plugin. The reason the probability of this risk occurring was rated low is because its development is backed by the Roy Rosenzweig Center for History and New Media at George Mason University and is funded by the Sloan Foundation. This risk will be mitigated using a contingency of identifying another suitable plugin prior to project start.

Risk 006: We have identified the risk associated with insufficient resources in the INTE 5160 course as a

medium priority. Insufficient resources could mean one of two events: 1) enrollment is so low that the course is postponed until another semester, in which case the project is delayed, or 2) enrollment is so low that there are more project roles and responsibilities than there are students to fulfill them. The probability of this risk occurring is low. The reason it is rated at low is because volunteers will be recruited and extra credit could be awarded for assistance with the project. The impact of risk 006 is rated as high. If the project team is nonexistent or insufficient in numbers, the project will be postponed.

Risk 007: We have identified the risk associated with loss of project team members as a medium priority. The

probability of this risk occurring is medium. The reason it is rated at medium is because the team will be built of M.A. students who have a solid commitment to their courses. The impact of risk 007 is rated as medium as loss of a project manager or team members can result in delays and the need for retraining.

Risk 008: We have identified the risk associated with the project team member’s skill level or lack thereof as a

medium priority. The probability of this risk occurring is medium. The reason it is rated as medium is because the team will be built using ILT M.A. students who have passion for the subject matter and/or

13


experience with it. The impact of risk 008 is rated as medium. Different skill levels can affect the quality and features of a project by varying degrees.

Risk 009: We have rated the risk associated with the analysis and revision of Diigo taking longer than expected

as low. Analysis of the Diigo site is an important first step in curating the material to be moved to the new website. The probability of this occurring is medium. The reason this is medium is because the Diigo site is growing and links may change over the course of the semester. At this time we don’t know how many redundant or obsolete sites which may take longer than expected.

Risk 010: We have identified the risk associated with project quality as a medium priority. The probability of this

risk occurring is low. The reason it is rated medium is because we can assume that many of the people taking this course will not have a PM background; this could affect the flow of the project and its schedule. Additionally, the skill level of key players on the team will be an unknown until the project is well underway. The impact of risk 010 is rated as medium. Depending on the size of the gap between expectations and results the impact could vary. In this case, we chase medium because the team will be M.A. students who have most likely proven proficient or better when it comes to quality and adherence to expectations.

Risk 011: We have identified use requirement as a medium risk. The probability of this occurring is medium as well. Use requirements that change once the project is underway would most probably force a redesign of the scope statement and project documentation and delay or halt the project.

Low Priority Low priority is defined by any combination of low/medium or low/low.

Risk 005: We have identified this risk as low. The probability of this occurring is also low. The reason this is rated as low is because the analysis team will meet with the PM and select the tags that will be used before the designers begin the site build. The team will most likely come to consensus after viewing similar tags on other PM websites to determine industry standard.

Risk Management Activities All risks will be recorded in a risk log and reviewed regularly. Ongoing risk management will include the following activities: Staffing: This project will be staffed by students in the ILT program. To manage the risks involved in working

with students, including lack of expertise, capacity and availability, we have incorporated students working on teams for each of the staff roles. Each team will have specific individual’s assigned activities

14


to ensure accountability for completion of activities. This team approach supports collaborating with expertise and capacity to complete the activities on time.

Capacity of staff: To mitigate the risk there won’t be enough staff capacity to complete this project we

recommend that work on this project be offered as independent study credit. This will allow students to earn elective independent study credit at the same time increasing the capacity of staff for this project. This provides students outside of the ILT program a way to earn credit that could be applied toward a different course of study and at the same time ensure the project would have the staff capacity to be successful. Students that would take this course as independent study would then be able to include the completed project in their student portfolios.

Controlling: Countermeasures that are initiated will be monitored and controlled by the project manager to make sure that they do not go beyond the scope of the project plan. Regular meetings will be scheduled by the project manager to review and manage the identified risks.

Monitoring: The project will be monitored by the project manager at all times for potential risks and if an identified risk becomes a problem, contingency plans will be put into action.

Ongoing workflow: To manage risk throughout the project, a system of end of stage meetings will be

conducted. These meetings provide check in times throughout the project to review what is working, what needs to change and inform adjustments to the work activities as the project evolves.

Review Processes: Throughout the project, review cycles are incorporated to ensure that the deliverables meet

the stated objectives. By incorporating review and sign offs along the way, there is a heightened opportunity to identify and address issues immediately.

Style Guide, Diigo Curation Guidelines and Design Document: These documents will ensure consistency in the

look and feel of the website and desired functionality is achieved.

Schedule: Additional time has been built into the schedule to control the risk of running over deadlines. During the end of phase meetings a review of schedules will be completed with updated projections for completion and communications with the sponsor to determine the best options for either meeting deadlines or extensions needed to ensure a quality product.

Quality Assurance Plan Quality assurance will be part of the risk management process to ensure that the deliverables and website production will meet the needs and standards of the client. This team will provide feedback to the development team, feedback around functionality, navigation, and spelling and grammar. This team will not provide feedback on design, as that has already been approved at this point. The quality assurance members will perform the task listed below and notify all team members. Identifying and recognition of typos and a lack of clarity Communicating with team members regarding errors and suggestions for corrections Thinking abstractly in order to quickly solve issues

15


Communication Plan

Who What When How To Whom

Project Sponsor Expectations and project goals

Before, during at the end of project

In person/ Conference call

Project manager and project team

Project Manager Overall project status, milestones Weekly and monthly

In person/ Conference call

Project Sponsor, Project team members

Web Analyzers

Analyze Diigo, tagging and curation of site, Audience survey

As needed according to project schedule In person/ Email

Project manager and designers

Designers

Content from web analysts create look and feel of site

As needed according to project schedule

In person/ email/ live hangout

Project manager, developers. And quality assurance teams

Developers

Create functional website, troubleshoot technical issues,


In person/ email/ live hangout

Project manager designers, quality assurance, communications teams

Quality Assurance Staff

Test website, provide feedback, identify and fix typos, communicate with team members on corrections


In person/ email/ live hangout Project manager, all teams

Communications Team

Communicate with external contacts, create promotional advertisement, produce survey from end users


In person/ email/ live hangout Project manager, all teams

16


References Carroll, J. (2012). Effective project management in easy steps (2nd ed.). Leamington Spa, Warwickshire, UK: In

Easy Steps Ltd. DeMers, J. (January 7, 2014). Your Guide to Content Curation for SEO. Retrieved from Search Engine Journal:

Web. 26 June 2014, http://www.searchenginejournal.com/guidecontentcurationseo/80773/ Kapor, M, n.p., Brainyquote.com n.d. web (26 June 2014)

http://www.brainyquote.com/quotes/quotes/m/mitchellka163583.html

17

http://www.google.com/url?q=http%3A%2F%2Fwww.searchenginejournal.com%2Fguide-content-curation-seo%2F80773%2F&sa=D&sntz=1&usg=AFQjCNGrKfHRVg1ujk70Aka9Qzppb5mhEw

http://www.google.com/url?q=http%3A%2F%2Fwww.brainyquote.com%2Fquotes%2Fquotes%2Fm%2Fmitchellka163583.html&sa=D&sntz=1&usg=AFQjCNFKplY51jShC5J8fMa_PRgA2cI6kw

INTE 5160 Summer 2014 Project Management Knowledgebase ...€¦ · INTE 5160 Summer 2014 Project...

Documents

Transcript of INTE 5160 Summer 2014 Project Management Knowledgebase ...€¦ · INTE 5160 Summer 2014 Project...