Article Contents
Research is the cornerstone of many innovations. It helps bridge the gap between the present and the future and new technologies, strategies, resources, and ideas are explored. Despite the importance of research, evaluating how research findings fit with the customer’s business model is often underappreciated.
In order for research to deliver the results need to be valid outputs:
- Effective
- Relevant, and
- Supported

Outputs that cannot be integrated into existing structures, processes, and technologies are considered disruptive and carry significantly more implementation risks.
These disruptive outputs also represent an opportunity for increased rewards if their value is realized. Product differentiation may not be enough as customers evaluate the innovation against the three criterion mentioned above. Innovations that are unable to differentiate themselves (price, cost, quality, impact, or value, etc.) are less likely to be ‘adopted.’
Research innovation requires a process based approach that insures that the opportunities explored will solve an existing issue or problem.

In academia, these issues may largely represent questions and gaps in information. In the technology space, they may involve functionality, ease of use, or interactivity (to name a few).
Understanding the problem becomes central to developing an effective research program and structuring the product development cycle.
The following components should be included in every research project management plan.
Research Project Management Using MSProject

The following project structure was built out in Microsoft Project 2016. It includes a generic framework for planning your next research project.
This hypothetical research project was structured around the five project management process groups. These groups are Initiation, Planning, Execution, Monitoring & Controlling, and Closeout.
Task Name | Duration | Start | Finish | |
Stage 1: Initiation | 15 days? | Fri 18-03-09 | Thu 18-03-29 | |
Human Resources | 4 days? | Fri 18-03-09 | Wed 18-03-14 | |
Identify Stakeholders | 4 days? | Fri 18-03-09 | Wed 18-03-14 | |
Establish Project Committees: Finance, Project, Ethics | 1 day? | Fri 18-03-09 | Fri 18-03-09 | |
Establish Project Working Groups | 3 days | Mon 18-03-12 | Wed 18-03-14 | |
Establish Working Groups | 3 days | Mon 18-03-12 | Wed 18-03-14 | 4 |
Establish Roles & Responsibilities | 3 days | Mon 18-03-12 | Wed 18-03-14 | |
Evaluate Bid Op (if relevant) | 15 days | Fri 18-03-09 | Thu 18-03-29 | |
Confirm Deliverables | 1 day | Fri 18-03-09 | Fri 18-03-09 | |
Confirm Timeline | 3 days | Mon 18-03-12 | Wed 18-03-14 | 9 |
Confirm Budget | 5 days | Thu 18-03-15 | Wed 18-03-21 | 10 |
Submit for Internal Review: Ethics, Budget, & Strategy | 6 days | Thu 18-03-22 | Thu 18-03-29 | |
Ethics Committee Review | 3 days | Thu 18-03-22 | Mon 18-03-26 | 11 |
Submit Bid Proposal (if relevant) | 2 days | Tue 18-03-27 | Wed 18-03-28 | 13 |
Bid Decision – Deadline (if relevant) | 1 day | Thu 18-03-29 | Thu 18-03-29 | 14 |
Stage 2: Planning | 25 days? | Fri 18-03-30 | Thu 18-05-03 | 15 |
Charter | 25 days? | Fri 18-03-30 | Thu 18-05-03 | |
Project Scope Statement | 10 days | Fri 18-03-30 | Thu 18-04-12 | |
Scope Management Plan | 10 days | Fri 18-03-30 | Thu 18-04-12 | |
Deliverables | 3 days | Fri 18-03-30 | Tue 18-04-03 | |
Budget | 3.3 days | Wed 18-04-04 | Mon 18-04-09 | 20 |
Schedule | 3 days | Tue 18-04-10 | Thu 18-04-12 | |
Experiment Design | 13 days? | Fri 18-04-13 | Tue 18-05-01 | 22,19 |
Goals | 3 days | Fri 18-04-13 | Tue 18-04-17 | |
User Demographics | 4 days | Fri 18-04-13 | Wed 18-04-18 | |
Study Setting | 7 days | Fri 18-04-13 | Mon 18-04-23 | |
Experiment Design | 3 days | Wed 18-04-18 | Fri 18-04-20 | 24 |
Data Collection | 5 days? | Tue 18-04-24 | Mon 18-04-30 | 26 |
Data Management Plan | 5 days? | Tue 18-04-24 | Mon 18-04-30 | |
Calculations | 1 day? | Tue 18-04-24 | Tue 18-04-24 | |
Instruments & Tools | 5 days | Tue 18-04-24 | Mon 18-04-30 | |
Consents | 5 days | Tue 18-04-24 | Mon 18-04-30 | |
Ethical Concerns & Responses | 1 day? | Tue 18-05-01 | Tue 18-05-01 | 28 |
Training | 2 days | Wed 18-04-18 | Thu 18-04-19 | |
Pilot Study | 4 days | Thu 18-04-19 | Tue 18-04-24 | |
Communications Plan | 2 days | Fri 18-03-30 | Mon 18-04-02 | |
Stakeholder Management Plan | 2 days | Fri 18-03-30 | Mon 18-04-02 | |
Risk Management Plan | 2 days | Wed 18-05-02 | Thu 18-05-03 | 33 |
Recruitment Management Plan | 3 days | Thu 18-04-19 | Mon 18-04-23 | 25 |
Stage 3: Execution | 9 days? | Fri 18-05-04 | Wed 18-05-16 | 16 |
Training | 2 days | Fri 18-05-04 | Mon 18-05-07 | |
Pilot Project | 7 days? | Tue 18-05-08 | Wed 18-05-16 | 41 |
Implement Pilot Project | 5 days | Tue 18-05-08 | Mon 18-05-14 | |
Analysis & Reporting | 2 days? | Tue 18-05-15 | Wed 18-05-16 | |
Analyze Results & Report to Committee | 1 day? | Tue 18-05-15 | Tue 18-05-15 | 43 |
Committee & Working Group Updates | 1 day? | Wed 18-05-16 | Wed 18-05-16 | 45 |
Update Project Plan | 1 day? | Wed 18-05-16 | Wed 18-05-16 | |
Stage 4: Monitoring & Controlling | 33 days? | Thu 18-05-17 | Mon 18-07-02 | 40,47 |
Launch Formal Project Plan (w/ Updates) | 20 days | Thu 18-05-17 | Wed 18-06-13 | |
Recruitment | 15 days | Thu 18-05-17 | Wed 18-06-06 | |
Consents | 5 days | Thu 18-06-07 | Wed 18-06-13 | 50 |
Data Collection | 6 days | Mon 18-06-25 | Mon 18-07-02 | 51 |
Data Sampling QA | 6 days | Mon 18-06-25 | Mon 18-07-02 | 56,54 |
Project Status Reporting | 8 days? | Wed 18-06-13 | Fri 18-06-22 | |
Working Group Meetings | 1 day? | Wed 18-06-13 | Wed 18-06-13 | |
Committee Meetings | 1 day? | Thu 18-06-14 | Thu 18-06-14 | |
Prepare to Close Project | 1 day? | Fri 18-06-22 | Fri 18-06-22 | |
Stage 5: Closeout | 8 days? | Tue 18-07-03 | Thu 18-07-12 | 48 |
Reports & Presentations | 5 days | Tue 18-07-03 | Mon 18-07-09 | |
Closeout Checklist | 1 day? | Tue 18-07-10 | Tue 18-07-10 | 59 |
Lessons Learned Documentation | 1 day? | Wed 18-07-11 | Wed 18-07-11 | 60 |
Transfer Project Deliverables | 1 day? | Thu 18-07-12 | Thu 18-07-12 | 61 |
Project Sequence Activity
The following activity involves sorting the images according to the project planning and implementation sequence. Hint: The project sequence is aligned with the five project management process groups.
Delivering Research Projects as a Product
Project management does not represent a one size fits all approach. Each project is individually tailored to fit the tools, culture, resources, and goals of the project environment. In contract settings, this tailoring presents an additional challenge. The project structure may only exist within the project office. A completely different structure and process is used in the business customer’s environment.

The following project management tools can deliver additional value. They act as mechanisms that increase alignment, engagement, and feedback across the project life-cycle. These are particularly useful in distributed and virtual networks. They are also helpful when working with new customers unfamiliar with the project management framework.
Conclusions

Project structure will often vary. It depends on the type of products being developed. It also depends on how the product will be used and the process used to deliver the project. A waterfall approach is used when the project team can confidently plan the project stages in advance. The risks, budget, and resources are already known.
An agile approach is used when requirements need confirmation throughout the project life-cycle. Specifications and risks are confirmed in an iterative fashion. The agile mindset supports sprints and scrum. It fits the software development life-cycle model. The waterfall approach is often considered a fit for project, strategic, and operations planning.
Understanding what approach is needed can differentiate businesses. Some are able to deliver a project successfully, and some struggle with cost, quality, and scope.
Research projects are particularly difficult. Collecting the wrong data, metrics, or using the wrong process or model can invalidate the entire study.
Statistical tools are available to strengthen insights in the midst of poor quality control but not poor planning. The initiation and planning stages are crucial to project success and are even more critical in research projects.
Research Management Plan
The following tool is available for creating the first draft of your research management plan. Once all of the fields are completed you have the option to export and download the document. The tools is structured similarly to the above template and follows the five project management process groups.

Check out the interactive article, Knowledge Management in Sharepoint!
Travis Barker, MPA GCPM
Innovate Vancouver
Innovate Vancouver is a Technology and Business Innovation Consulting Service located in Vancouver, BC. Contact Innovate Vancouver to help with your new project. Innovate Vancouver also gives back to the community through business consulting services. Contact us for more details.