1. Digital Delivery Dashboard
Kick Off Meeting

2. Agenda Project Overview Dashboard Description High Level Scope Roles
Timeline & Deliverables
Dependencies, Assumptions & Risks
Considerations
Q&A

3. Project Overview
Create a digital dashboard and process for disseminating information about Digital Delivery’s products, strategic initiatives and processes, including, but not limited to:
Product Roadmaps
POCs, pilots, prototypes and focus groups
Impending launches
Operational Processes
Digital product usage and revenue information

4. Dashboards What is a dashboard?
A user interface that organizes info from multiple components and presents the info in an easy-to-read and unified fashion.

5. High Level Project Scope
In Scope:
Compiling and prioritizing a list of dashboard requirements based on user interviews from key stakeholders.
Compiling and assessing a list of possible software for use.
Identifying Minimally Viable Product (MVP) for first launch.
Develop a POC.
A prototype site utilizing the selected technology will need to be created utilizing real workflows.
Working team to help draft and test technology/process stemming from the dashboard creation.
Implementing MVP for first launch.
Rolling out dashboard to all users.
Out of Scope:
Technology solutions that will require funds from Digital Delivery budget.
Aha! training and standardized Aha! process development for the product management teams.
Creating a repository for Digital Delivery product and process storage.
External site for partners/vendors.

6. Digital Delivery Dashboard
Workstreams
Steering Team/Key Stakeholders
Hiral Lai
Tom Speyer
Dan Wood
Paul Labay
Nancy Gerome
Amanda Wainer
Working Team Lead/Project Manager
Tera Moore
Put in some comments on role on the word doc.
Working Team
Development/QA
Development/UX
Calvin Daniel
Nikki Timmons

7. Project Team & Roles Working Team Steering Committee Project Manager
Tech analysis and recommendation.
Provide technical requirement specs.
Provide UX guidance.
Dashboard development & QA.
Bubble up technical issues/conflicts to PM as they arise.
Project Manager
Oversee overall project and ensure project goals are met.
Requirements (gathering, defining and prioritizing).
Provide project documentation (Scope, requirements, dashboard procedures).
Provide
Steering Committee
Requirements (defining and prioritizing).
Inform PM & working team of requirement changes.
Provide feedback.
Assist PM in obtaining reports and data for the dashboard.

8. Timeline & Deliverables
March 1 – May 1
◦Interviews
◦Requirements
◦Tech Analysis & Recommendation
◦Scope developed
◦Kick Off Meeting
◦Wireframes
◦MVP
◦POC developed
May 2 – July 1
◦Prototype developed
◦Report/Link owners documented
◦Prototype tested
◦Dashboard update process documented.
◦Steering Committee approves dashboard soft launch/socialization.
July 5 – July
◦Soft launch feedback reviewed and prioritized.
◦Dashboard workflows & documentation reviewed and modified.
◦Steering Committee approves updated dashboard for division-wide launch.
◦Dashboard pushed live.

9. Dependencies, Assumptions & Risks
As always, availability of team members’ time is at a premium.
Requirements for dashboard may be complex and require the timeline to be pushed out.
Assumptions:
New processes will require refinement even after implementation.
Post-launch further links/reports will be added on a rolling basis.
Risks:
Research may reveal that one centralized location is not feasible or recommended for all internal users.
Research may reveal that a significant portion of data cannot be automated without additional investments.

10. Considerations for Deliverables
This project is being developed specifically for internal Wiley employee use.
Technology currently available and in use at Wiley is preferred but not mandatory.
Site(s) should be accessible without VPN.
There will need to be new workflows / processes developed to meet these deliverables.
A Digital Delivery repository has been identified as a need and may be accomplished within this project via dashboard links.
The product management team has identified a need for a streamlined Aha! process but it falls outside of the scope of this project.
The need for an external info site for vendors/partners has been identified but falls outside of the scope of this project currently. If pursued, an external site may require a separate technology and process.

11. Q&A

12. Recommended Tech & MVP Recommended Software Recommended Links/Reports
WordPress
Open source & free
Easy set up.
Can be updated in-house with relative ease.
Design and functionality flexibility.
Responsive.
Recommended Links/Reports
Product Management Reports – link to Aha and Excel doc.
Customer Pain Index (validation, uptime)
Solutions Delivery open project list.
Articles of interest.