Practicing Agile As a BA

Transcription

1 2014 BA Convention Practicing Agile As a BA Presented by: Jagruti Shah Associate Business Consultant Mastek Ltd

2 2014 BA Convention 2 Role of BA in Agile What is Agile? What does Agile mean for a Business Analyst? What does Business Analyst aim for? How to achieve 3 C s (Card, Conversation & Confirmation)?

3 2014 BA Convention 3 Key Takeaways... Agile Atmosphere Grooming product backlog INVEST understood and practiced Lean UX collaborative designs with UED Encourage collaboration

4 2014 BA Convention 4 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

5 2014 BA Convention 5 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

6 2014 BA Convention 6 Business Needs 3. Build Reusable Platform Across Government Projects

7 2014 BA Convention 7 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

8 2014 BA Convention 8 My Agile Journey Foundation On Board Detailing User Story

9 2014 BA Convention 9 On Board AGILE ATMOSPHERE

10 2014 BA Convention 10 The Room - Forming the Agile Atmosphere Release Wall Projector Scrum Board Avatar White Board Open Desk

11 2014 BA Convention 11 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

12 2014 BA Convention 12 Foundation GROOMING PRODUCT BACKLOG

13 2014 BA Convention 13 Product Click to edit Backlog Master text Initial styles Structure & Challenges Initial Product Backlog Multiple BA s & multiple product backlogs Dependencies not clear Technical complexity & team confidence not known Development team s involvement missing Nonfunctional requirements missing

14 2014 BA Convention 14 Product Click to edit Backlog Master - text Our styles Approach Story Gathering Workshop Before After Added Fields

15 2014 BA Convention 15 Value Effort Map (VEM)

16 2014 BA Convention 16 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

17 2014 BA Convention 17 Detailing a User Story INVEST UNDERSTOOD & PRACTICED

18 2014 BA Convention 18 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 Fringe cases with PO's agreement UX behavior to be BA-UED aligned with user Pairing story Time-boxing Definition of done 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

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

20 2014 BA Convention 20 Detailing a User Story LEAN UX COLLABORATIVE DESIGN WITH UED

21 2014 BA Convention 21 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 Discrepancy collaboration between Support teams wireframe & during development criteria Peer/PO reviews Exploratory testing UX war room Central repository for business Multiple rules, BA-UED validations, error messages pairs Requirement team meeting

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

23 2014 BA Convention 23 UX War Room UX War Room Living Style Guide

24 2014 BA Convention 24 Collaboration ENCOURAGE COLLABORATION

25 2014 BA Convention 25 Collaboration Click to edit Master Challenges text styles v/s Approaches Collaboration with Relevant Lengthy/unwanted discussion points discussion in Agile ceremonies Time-boxing Stakeholders Take a photo & 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

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

27 2014 BA Convention 27 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

28 2014 BA Convention 28 Key Takeaways Agile Atmosphere Grooming Product Backlog INVEST Understood & Practiced Lean UX Collaborative Designs with UED Encourage Collaboration

29 Learn more BA Convention

30 2014 BA Convention Thank You! Speaker : Jagruti Shah ID : jagruti.shah@mastek.com Learn more.