A Day in a life of a Product Owner
Activity
8:00 a.m. Attend the daily standup meeting for the team. Listen to the development team share progress and barriers. Share your barriers and progress. Offer to help or collaborate to remove the barriers with the team. Listen for the team’s understanding of value.
8:15 a.m. Prepare for the day by thinking about what you heard in the standup and what will provide the most value today.
8:30 a.m. Review user stories and requirements submitted by others. Analyze where they fit into the value and the roadmap. Determine if they should be added to the backlog. Initiate action to resolve team impediments, reaching out to internal departments, clients, and stakeholders to close the gap for the team.
9:00 a.m. Plan backlog refinement session for the following week. What activities will you facilitate to get the best engagement? How will you ensure the team is focused on value and the roadmap?
10:00 a.m. Catch up on the latest industry and company news. Think about how the events (internal and external) may impact the product, the roadmap, and the release plan. Do the priorities change based on news events, internal company happenings, or industry news?
11:00 a.m. Review and test mid-sprint stories and give feedback to the team. Feedback should be focused on user-centered thinking, design, and will the user value the new functionality?
12:00 pm lunch with teammates
1:00 p.m. Prep for the next day’s story writing session. How will you set the stage and context for a productive story writing session that aligns with the product vision?
1:30 p.m. Meet with the development team to talk about the stories currently in progress. Discuss the context, acceptance criteria details, and factors that contribute to minimum viable product (MVP).
2:00 p.m. Attend the sprint planning session to provide context and minimum viable product information for story estimating.
3:00 -5p.m. Test the latest updates of user stories from the development team. Provide feedback to the team, update the acceptance criteria if needed, move the stories to done, and update comments in the Jira, Rally, Azure for the developers of tester for the next day discussion in the meeting after standup to clear any clouds.
6pack App Example
Target group: Health fitness club members on the go
Goal: To get information quickly without making a phone call and to build a deeper relationship with the member
Needs: A mobile app that is easier than calling, emailing, or using a full website to get basic club interactions and information
Value: Faster and more convenient to the club member, and will lower costs for the club
Key features: View Club Information, View Class Schedules, Register for a Class, Schedule an Appointment with a Trainer, and Motivational Notifications for Healthy Living and Fitness Goals
