agiletour.org

  • Português
  • 简体中文
  • 繁體中文
  • Deutsch
  • English
  • Español
  • Français
  • 日本語
  • Latviešu
  • Lietuvių
  • Русский

Submitted Conference Content

Full name

Amoli Upadhye

Job Product Owner
email amoliupadhye [at] gmail [dot] com
Company Tata Consultancy Services (TCS)
City (Country) Mumbai
Time 45'
Type of Conference Conference > 100 attendees
Level Everybody

Career path for PO’s

Biography

I am working as a Product Owner (PO) at Tata Consultancy Services (TCS) and experienced in working with a large client - vendor relationship. I have a total IT experience of 7+ years. Being a vendor PO does put additional layers of stakeholders in my requirements life cycle, but we have fine tuned the model over some time now and have successfully customized it. I absolutely enjoy my role and am keen on exploring how can I grow in my career while still a PO. IT PO's anyone ? I like improving my problem solving skills while working on IT projects as a PO - a function that I find very dynamic

Description

Scrum defines her Product Owners (PO’s) as a representative of the actual users and someone who is accountable for delivering business value and thus the ROI. A lot of us have our own interpretations of this definition. Interpretations, which are influenced by ‘our’ teams, company policies, vendor – client relationships and the PO you have to go back to each day in your office. This has carved versions of the perfect, or worse, a far than perfect PO in everyone’s mind. The IT industry is seeing changes it never did 10 years back and like our agile teams, is responding to changes its business stakeholders are demanding of it. As a result, we are serving new clients, developing solutions for newer domains, honoring contracts that are more strategic than ever and wearing new hats. During this journey, we have evolved away from text book definitions of our roles and adopted versions that suit our developers and sponsors better. In agile words, we have responded to changes than follow traditional definitions. Has that caused barriers between PO’s and rest of the IT world? If so, how can we announce the evolution and show – off our new avatars? Such flavors of PO role are lesser discussed in the corridors of Scrum world; surprisingly every agilist I have spoken to is curious and has questions about a PO’s responsibilities and how would they propel a PO high on a growth / career chart in future. As a PO myself, I have been observing what options of growth does an organization offer us after we have styled ourselves, like explained above, to its business requirements. How can we thus grow with our products / programs? I would like to present my observations and findings about these questions through this session.

Prerequisites

Basic of Scrum roles

Benefits for the attendees

1. Appreciate various flavors of PO roles. One size does NOT fit all 2. Understand how POs can grow with their products / programs 3. Explore opportunities available within organizations for the next level of product ownership

Go to the submission page!