16 October 2017 | Management and Business Improvement
If you missed the first series of the Scrum guide read it here.
Seven competencies you need to make you a successful Product Owner.
Scrum teams must be self-organizing with all the competencies and emotional intelligence required to master their work without reliance on direction from above. In my previous article I briefly introduced the three key Scrum roles, that of, Product Owner, Development Team, and Scrum Master.This article focusses on seven core competencies you will need to be the best Product Owner (PO) you can be.
1. You must represent the customer, become the Voice of the Customer (VOC) and maximize business value, as well as ensuring that the team appreciate how their deliverables impact the business.
2. As PO, you must make key decisions and optimize product value and the teams’ work by setting the priorities for the items in the Prioritized Product Backlog. For this you require immense functional knowledge of your business and know what your business needs, as the development team will look upon you to get answers related to requirements.
3. As the business subject matter expert, you define the Project Vision Statement that serves as the inspiration and focus for the entire project.
4. You must ensure that the Development Team understands items in the Product Backlog by making it visible, transparent, and clear to all, showing what the team will work on next.
5. You must play a key role in charting the release calendar. Based on your thorough understanding of the business strategies, market trends, and end-user needs, you need to predict with reasonable accuracy when a set of functionalities will be relevant to the customers.
6. You must provide visibility to business leadership through close engagement with the team and working with them throughout the development cycle, helping in prioritization, understanding constraints, mitigating risks, and providing requirement clarifications.
7. You must ensure that the identified benefits are achieved through excellent change management, during the iterations and on project completion.
Author: Corrie Jordan