ݺߣ

ݺߣShare a Scribd company logo

Eleonora Budanova “BA+PM+DEV team: how to build the synergy”

•Download as PPTX, PDF•
•
Sigma Software
Sigma Software

This document discusses how a business analyst helped improve synergy between the BA, PM, and development team on a project. The business analyst first assessed the project complexity, history of changes, and their own strengths. They discovered issues like an unrefined product backlog, estimates not being met, and changes during sprints. To address this, the analyst held retrospectives and 1:1 meetings. They created requirements templates with metadata, purpose, acceptance criteria. This provided clear requirements and decreased stress and scope changes. As a result, sprints delivered fully, the team was happier, and the client said the templates met their needs and communication was consistent.

1 of 15
Download to read offline
BA+PM+DEV team: how to build the synergy SIGMA SOFTWARE
Eleonora Budanova Business analyst at Sigma Software LinkedIn: 2 ABOUT ME
What is Business Analysis? 3
WHAT IS BUSINESS ANALYSIS? Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. 4
BUSINESS ANALYSIS IS EVERYWHERE. THE QUESTION IS, WHO’S DOING IT? 5
ENTER TO PROJECT 6
My first steps are assessment of: • The complexity of the project, • The history of changes in the project, • Own strength. 7
What did I elicit? 8
What did I elicit? 9 Product Backlog Sprint Backlog Development mess Changes in Sprint Backlog Delivery of only a part of initial Sprint Backlog Team & Client dissatisfaction
How to initiate? • Retrospective • Root Cause Analysis • 1:1 meeting meeting with PM 10
11 REQUIREMENTS STRUCTURE USER STORY ELEMENTS Metadata:  Status Draft / Verified / Validated  Created date & Updated date  Team verified: Backend / Frontend / QC  Link to ticketing system  Source Purpose  Overall view on the business need which is covered by this new feature. Card  An active-verb goal phrase Conversation  A well-written user story invokes conversation among the team. Confirmation  Acceptance criteria define the boundaries of a user story and help verify and validate the solution met the intended user need.
From fail to success 12 Product Backlog Requirements timely detailed description and refinement Estimation of requirements Sprint Backlog Calm Development Perfect delivery Team & Client are happy Product Backlog Sprint Backlog Development mess Changes in Sprint Backlog Delivery of only a part of initial Sprint Backlog Team & Client dissatisfaction
OUTCOMES  All processes are clear.  Published on wiki.  The team stress level is decreased.  Less negative points on retrospective.  No sprint scope creep.  Requirements are clear. 13
OUTCOMES A happy client ”I've reviewed the templates and am happy to proceed / confirm this is more than adequate for my needs. PM and the team are fantastic and consistent communicators in our weekly meetings” 14
THANK YOU!

More Related Content

Eleonora Budanova “BA+PM+DEV team: how to build the synergy”

  • 1. BA+PM+DEV team: how to build the synergy SIGMA SOFTWARE
  • 2. Eleonora Budanova Business analyst at Sigma Software LinkedIn: 2 ABOUT ME
  • 3. What is Business Analysis? 3
  • 4. WHAT IS BUSINESS ANALYSIS? Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. 4
  • 5. BUSINESS ANALYSIS IS EVERYWHERE. THE QUESTION IS, WHO’S DOING IT? 5
  • 7. My first steps are assessment of: • The complexity of the project, • The history of changes in the project, • Own strength. 7
  • 8. What did I elicit? 8
  • 9. What did I elicit? 9 Product Backlog Sprint Backlog Development mess Changes in Sprint Backlog Delivery of only a part of initial Sprint Backlog Team & Client dissatisfaction
  • 10. How to initiate? • Retrospective • Root Cause Analysis • 1:1 meeting meeting with PM 10
  • 11. 11 REQUIREMENTS STRUCTURE USER STORY ELEMENTS Metadata:  Status Draft / Verified / Validated  Created date & Updated date  Team verified: Backend / Frontend / QC  Link to ticketing system  Source Purpose  Overall view on the business need which is covered by this new feature. Card  An active-verb goal phrase Conversation  A well-written user story invokes conversation among the team. Confirmation  Acceptance criteria define the boundaries of a user story and help verify and validate the solution met the intended user need.
  • 12. From fail to success 12 Product Backlog Requirements timely detailed description and refinement Estimation of requirements Sprint Backlog Calm Development Perfect delivery Team & Client are happy Product Backlog Sprint Backlog Development mess Changes in Sprint Backlog Delivery of only a part of initial Sprint Backlog Team & Client dissatisfaction
  • 13. OUTCOMES  All processes are clear.  Published on wiki.  The team stress level is decreased.  Less negative points on retrospective.  No sprint scope creep.  Requirements are clear. 13
  • 14. OUTCOMES A happy client ”I've reviewed the templates and am happy to proceed / confirm this is more than adequate for my needs. PM and the team are fantastic and consistent communicators in our weekly meetings” 14