Value & Role of Business Analyst in Agile. Presented by: Jagruti Shah Associate Business Consultant Mastek Ltd

Transcription

1 Value & Role of Business Analyst in Agile Presented by: Jagruti Shah Associate Business Consultant Mastek Ltd

2 Our Click Focus to edit Master using Agile text styles Principles Build software quickly Keep requirements flexible Test as it is built Reducing waiting time

3 Agile Manifesto The Agile Manifesto is a formal proclamation of 4 key values and 12 principles to guide an iterative & people-centric approach to software development

4 Business Click to edit Analysis Master text in Agile styles 6. Deliver business value 5. Holding larger context of business case 1. Just-in-time analysis Agile BA Value & Role 4. Short iterations 2. Just enough documentati on 3. Continuous Coversation

5 Achieve Click to edit 3 C s Master of text Use styles Stories CARD AS A. I WANT TO SO THAT I CAN... Essence CONVERSATION Discussion CONFIRMATION Test case

6 Key Takeaways... Agile Atmosphere Grooming DEEP product backlog INVEST understood and practiced Lean UX collaborative designs with UED Encourage collaboration

7 Project Background About Identity & Access Management (IAM) with one of the UK clients in Health care domain A bespoke development covering User Click Registration to edit header & Access Management Services Credential Management Services Self-service Applications Audit & Reporting Services

8 About IAM Over 875,000 Registered users 2,000 Smartcard renewals per day 670,000 Users with smartcards EFFORTS 600MM 500 New smartcards per day 400,000 Digital signature based authentications a day DURATION 18M 70,000 concurrent users Registered users across 20,000 organizations

9 Business Needs 3. Build Reusable Platform Across Government Projects

10 Project Challenges Team of 50 - most of them new to agile Aggressive timelines with 4 releases planned Technically challenging due to use of open source Integration with smartcard readers & printers Zero downtime to migrate from old to new system Dependency of two more applications on it

11 My Agile Journey Foundation On Board Detailing User Story

12 On Board AGILE ATMOSPHERE

13 The Room - Forming the Agile Atmosphere Release Wall Projector Scrum Board Avatar White Board Open Desk

14 Agile Click to Atmosphere edit Master text - Benefits styles Focused teams Continuous & quick collaboration Teams with transparency & visibility Facilitating & preparing the team to perform their tasks effectively in Agile

15 Foundation GROOMING PRODUCT BACKLOG

16 Product Click to edit Backlog Master text Initial styles Structure & Challenges Initial Product Backlog Multiple product backlogs Un-ranked product backlog Development team s involvement missing Nonfunctional requirements missing

17 Product Click to edit Backlog Master - text Our styles Approach Story Gathering Workshop Before After Backlog grooming Workshop Added Fields

18 Value Effort Map (VEM)

19 Product Click to edit Backlog Master - text Benefits styles Identification of Dependency Technical complexity & Team confidence Spike stories, UI stories Non-functional stories Single & DEEP product backlog Transparency & visibility within the team Simplify the activity of planning & prioritization

20 Detailing a User Story INVEST UNDERSTOOD & PRACTICED

21 User Click Stories edit Master Challenges text styles v/s Approach Limited acceptance criteria Over-described Focus user more stories on conversation Slicing & Click dicing to edit header Separate Fringe cases UX behavior BA-UED to be aligned Pairing with user story Time-boxing Definition of readiness Collaborative design /grooming Not enough sessions backlog Design review reserve workshops with users Using white board extensively Preparing user journeys, portlets. Early Design grooming change

22 User Stories - Benefits Quality user stories with better designs Enough backlog reserve Engaging end users, development team Smart team with more conversation & ownership

23 Detailing a User Story LEAN UX COLLABORATIVE DESIGN WITH UED

24 BA-UED Click to edit Pairing Master text Challenges styles v/s Approaches Requirement Force 5-3 Pairs Align of UX BA-UED behavior + 2 UI developers with user story - working for 4 scrum teams Collaborative design sessions Design using white board dependency Continuous collaboration Discrepancy Support between teams during wireframe development & Peer/PO criteria reviews Exploratory testing UX war room Central repository for business Multiple rules, BA-UED validations, error messages pairs Requirement team meeting

25 BA-UED Click to edit Pairing Master text Benefits styles Better design solutions Shared responsibility of functional & non-functional requirements Quality delivery Central repository for UX artifacts Note:- This technique is only for projects having user interface.

26 UX War Room UX War Room Living Style Guide

27 Collaboration ENCOURAGE COLLABORATION

28 Collaboration Click to edit Master Challenges text styles v/s Approaches Collaboration with Relevant Lengthy/unwanted discussion points discussion in Agile Time-boxing ceremonies Tools Scrum board, projector Take a photo & Stakeholders at different Collaboration location using tools Following HEARTBEAT Unavailability Ensured availability of important with the help of stakeholders scrum master Proxy PO Culture with no hierarchy Discouraging Hesitation to s approach Continuous POs/SMEs conversation

29 Collaboration Benefits Building shared understanding DEEP product backlog INVEST user stories Better design approaches Leading to fast development & quality delivery

30 Realising Success..Performance...Usability... More than connection established using smartcards on 1 st day of Go-live Connections with Zero failures Printing time reduced by 75% Testimonial Amazed by Speed & Simplicity

31 Key Takeaways Agile Atmosphere Grooming Product Backlog INVEST Understood & Practiced Lean UX Collaborative Designs with UED Encourage Collaboration

32 Learn more.

33 Thank You! Speaker : Jagruti Shah ID : jagruti.shah@mastek.com Learn more.