Implementation Plan (proposal)

1. Bringing All Work on a Whiteboard

The initial phase is all about establishing the ground. It is recommended to use Archive to bring together all available materials in a free form, e.g. upload documents/reports, embed competitor’s / partners / customers' website pages, etc.

Use stickers to represent thoughts, decisions and requirements. Align the ideation stickers on a high-level timeline, classify across swim lanes, and outline dependencies.

2. Identify Requirements for Jira Projects

During collaborative work on Whiteboard, all pieces (sticker notes) are organized and interlinked, high level picture becomes clear → define Jira project requirements to accommodate the current workflows, while enabling future rapid growth.

Examples of what we need to understand

• Once requirements are articulated for Software and Business Jira Projects, I create traceability matrix document and start with system configurations → need org admin access to your Atlassian Instance

3. Transfer Work from Whiteboard to Jira Projects

• Once the Jira projects are configured, all stickers can be converted into issues of an appropriate type and assigned to a project. Couple videos demoing this process

• Creating a shared board reflecting dependencies across teams and alignment of all stakeholders' work to ensure hitting the Startup milestones.

• Testing → feedback → refinement.

4. Define Confluence Setup Requirements

• Shared Workspace to drive alignment around product and business goals. Contains documents such as Startup goals and vision, Product roadmap, Status reports/dashboards, Cross-project Kanban board

• Individual Workspaces: personal to-do list and calendar, embedded views to Jira projects and boards, quick links to 3rd tools (Google Docs, Sheets, etc.)

• Product Documentation: Product (MVP) roadmap, Customer interviews, Market research results, etc.

• Legal documents: Incorporation documents, employment contracts with e-signature capabilities, etc.

• Catalogues of recurring docs: retrospectives, meeting minutes, etc.

I suggest to create templates for all of your pages, in order to maintain your Confluence instance tidy and easy to navigate. A good idea is to have a defined content owner of each page, and create individual reminders to the owners to review content every xx months or even weeks while on an early stage.

5. Define Metrics and KPIs for EazyBI Dashboards and Reports

Based on the Startup’s requirements, custom dashboard can be configured to display key startup metrics and shared with potential investors (incl. non Jira users).

6. Documentation and Trainings

Scope and formats TBD.

Optional Apps

• Refined | No.1 Site-builder for Confluence, Jira & JSM For enhanced interface customization. Optimal for Intranet and knowledge management.

• Table Filter, Charts & Spreadsheets for Confluence | Atlassian Marketplace Key for PM if Confluence is the primary tool.

• http://draw.io for diagrams and charts