How does an #agile Friendly Work-space looks like?
March 17, 2018
#Kanban evolution Boards journey of a true #scrum team
April 11, 2018
Organization need to have an external product view (outbound) and an internal product view (Inbound) altogether regardless its size. Our organization will need precisely the combination of deep customer understanding with the ability to apply technology to solve customer problems that enables a strong product person.
But this can sometimes be overwhelming if it is misunderstood. Those two views need to be successfully integrated into an agile mindset in a fast-moving business environment.
On smaller projects the outbound view and the inbound view might be integrated into one person. Deep customer facing and understanding a long with close work with an agile team on day to day basis. This is hard!
On larger projects/products, it is common to have a high-level product manager setting the over-all direction for a product. (Outbound). understands the customer and he might be more customer-facing then the product owner (inbound). There will be several teams, each have their own product owner. Each product owner would maintain the backlog for their team. The product owner a more team-facing.
But, we don’t want the product owner to simply be a pass-through between the product manager and the team; the product manager and the product owner needs to work closely with each other as well and with the customer and the teams , to understand and prioritize (order) the stories in their team’s product backlog in way that supports the overall customer value , business value , the direction and goals.
| What | Product Manager | Product Owner |
| Tracks the overall market and competitive dynamics. | V | |
| Understands the business value and customer value and be able to Translate those to portfolio items | V | |
| Manages the long-term roadmap, involving sales, marketing, implementations, clients, prospects, partners, and other groups. The ideas are expressed as items , up to epics. | V | |
| Attends iteration demos and some stand-ups. | V | V |
| Supports other non-technical teams (such as sales, marketing, and channel). | V | |
| Leads product discovery process along with high level technical inputs | V | Attends |
| Leads requirements gathering effort on the epics as needed — consulting with product management, implementations, clients, and other stakeholders. | V | |
|
Work closely with the teams on a day to day basis and have many conversations with the team about requirements and about each user story. see demonstrations of work in progress on a daily basis |
V | |
| Documents story details based on the epics after reviewing with development. | V | |
| Attends scrum meetings including standups, retrospectives, and demos. | V | |
| Leads backlog grooming to decompose and estimate stories. | V | |
| Creates mockups and works with UX on design. | V | |
| Answer questions from developers and clarifies requirements. | V | |
| Documents the new feature for implementations and release notes. | V | |
| Write acceptance criteria. | V epic and item | Write acceptance criteria. – epic and user story |
| Demonstrate the latest iterations to customers (pre-release) and gathers feedback. | V | V |
Sources:
https://blog.aha.io/the-product-manager-vs-product-owner/
https://svpg.com/product-manager-vs-product-owner/
