We as a DevTeam

DevTeam consists of generalists specialists (T-shaped skill set) who can perform all work to create product increment as envisioned in the Sprint Goal. The size of DevTeam is 6±3. There is only one role in a DevTeam – Developer. Each member of DevTeam may have a specialization (say QA, front end, back end, database, etc.) but everyone is responsible to achieve the sprint goal. There are no sub-teams within DevTeam. DevTeam members follow good engineering practices. DevTeam members self-organize to achieve the sprint goal. DevTeam is a long running team and members are full time allocated to it. All of DevTeam members follow same norms and rules.

As a DevTeam, we own Sprint Backlog. During Sprint Planning Meeting, devTeam negotiates with Product Owner to keep its commitment for the sprint. Sprint Backlog represents the commitment of devTeam for a sprint. DevTeam members participate in Daily Standup and share their work and impediment if any. DevTeam is responsible to deliver product increment at the end of the sprint. DevTeam presents items to PO as soon as acceptance criteria is met. DevTeam members collaborate to complete the work. DevTeam only accepts the work as envisioned in the sprint backlog.

As a DevTeam, we participate in scrum ceremonies.  DevTeam actively participates in refinement activities to keep Product Backlog healthy. DevTeam estimates PBIs. DevTeam evaluates the technical feasibility of PBIs. DevTeam is responsible for all work to be done to deliver as committed in the Sprint Planning Meeting (in the form of Sprint Backlog). DevTeam participates in Sprint Review ceremony to collect feedback from stakeholders. DevTeam conducts Retrospective in the end of each Sprint with PO and SM to reflect on self. DevTeam helps PO to conduct Demo.

As a DevTeam, we strive for automation to keep effectiveness and productivity (velocity) curve upward. DevTeam adopts Agile engineering practices to keep the quality of product high. DevTeam members strive to learn new tools, techniques, technologies, and skills to develop T-shaped skill set. DevTeam members work closely with PO and SM to deliver consistently and effectively.

As a DevTeam we strive to deliver value with sustainable pace. DevTeam remains in conversation with PO throughout a sprint to get clarification on the Sprint Backlog Items. DevTeam has the clear understanding of Sprint Goal. DevTeam not only focuses on HOW but also knows WHY and WHAT. DevTeam is responsible for continuous delivery of valuable outcome. DevTeam is empowered to make the decision about the HOW part to complete the work as listed in Sprint Backlog. DevTeam manages information radiators. DevTeam continuously communicates with users.

As a DevTeam, we continuously educate ourselves and share learnings with technical, Lean, Agile and Scrum communities. We organize and participate in technical, Lean, Agile, and scrum oriented community events to facilitate understanding of technical, Lean, Agile, and scrum values and principles.

I as a Product Owner

As a Product Owner, I am responsible for Product Vision and its continuous evolution. I may not know everything about the product but I know, from where to get that information and how to manage competing stakeholders for limited resources and even manage conflicting views of stakeholders about the product. I am “go-to” person for product domain. I have business analysis skills. I negotiate priorities, scope, funding, and schedule. I own product roadmap as well as Product Backlog.

As a Product Owner, I do not drive technological decisions but understand and appreciate devTeam’s technical skills. I incorporate the technical wisdom of devTeam in Product Backlog’s prioritization in addition of stakeholders’ vision and wishes. I communicate WHY and WHAT of product so the Product Backlog Items. I share product vision with devTeam. I define Acceptance Criteria in collaboration with devTeam for every PBI.

As a Product Owner, I actively participate in scrum ceremonies. I lead Product Backlog Refinement effort with devTeam as well as stakeholders. During Sprint Planning Meeting, I offer Product Backlog Items to devTeam to be developed in current Sprint. I bring in subject matter expert o answer any query by devTeam. I only offer PBIs which are INVEST-able during part one of Sprint Planning meeting. I define Sprint Goal and convey the same to the team before or during sprint planning meeting. I ensure that I am always available to devTeam during Sprint. I accept PBIs during sprint as offered to me by devTeam provided they meet Acceptance Criteria. I have authority to reject any work performed during sprint. I can terminate sprint mid-way. I decide the content of demonstration of increment in collaboration of devTeam and actively participate in the same. I participate with devTeam to split PBIs. I don’t direct the team on how to perform its job. I drive release-planning effort with stakeholders and devTeam. I help the team to remove impediments.

As a Product Owner, I engage with stakeholders on the continuous basis to elaborate PBIs and create new ones. I interact with stakeholders to assign Business Value and prioritize PBIs. I utilize various techniques (Story Map, Impact Map, budgeting of story point to different stakeholders, and other techniques) to reach Minimum Viable Product, assignment of Business value, and prioritization of PBIs. I keep Product Backlog healthy – two to three sprint worth of stories are INVEST-able and prioritized.

As a Product owner, I continuously educate myself and share my learnings with Lean, Agile and Scrum communities. I organize and participate in Lean, Agile, and scrum oriented community events to facilitate understanding of Lean, Agile, and scrum values and principles.