Week 2 Product Management Team 2

PM Team 2 started the week on a great note basically because of the work we all put together to achieve Week one's task.

For Week 2, Our task is to use a Kanban board, manage cross-sectional teams to deliver the to-do app by Saturday. Document the process, lessons, retrospectives, and challenges.

We started by holding a meeting with the Product design team 2 to understand their task and the processs involved for the purpose of the kanban board. They briefed us on what they had done so far which was creating a survey (interview form) to understand the pain points of the users and also what solutions the users would want in the product. They promised to send the results from the survey which they did and also a breakdown of the processes involved in their task.

From the survey we came up with the following;

• Product Vision Statement which is "For students and employed individuals who must plan, prioritise and manage task effectively, our product is a new task management software that helps provide workflow management to achieve productivity. Unlike other task management softwares, we offer a product that enables you improve time management."

• The Problem which is Mismanagement of time which then leads to being unproductive.

• Competitor Analysis: Calendly which is a scheduling tool to create or set appointments, Clockify which is a time tracking software that helps you track work hours and Microsoft Todd which is a task management app that helps you create to do lists and allows you add notes.

• Market Industry Research: The survey created will be used to achieve it.

• User Research/Assumptions: Students want an app that helps them to be more effective and efficient. Employed individuals want an app that helps them achieve greater focus and also organise their priorities.

• Business Model Canvas
• User persona
• Product Strategy
• Product Roadmap
• Product Requirement Document
• Execution/MVP (Minimum Viable Product)
• Success Metrics/KPI

The challenges we faced includes the following;

• During the process of reaching out to the other teams we were supposed to work with, our team lead discovered that we only have the Product design team 2 to work with on this task.
• Not enough organisation of the task slowed us down and also confused us on how to carry it out.
• The communication channel was not clear about what team we were to liase with and this caused a bit of confusion.

The lessons learnt includes the following;

• Team work makes everything easier.
• Better Organisation would help us perform better at weekly tasks.

The retrospectives includes the following;

• We made do with the limited time we had and came up with our hashnode.
• The product design team could communicate and collaborate better.
• Tasks should be well organised and prepared.

We created the kanban board with the Product design team's task.