dcbadd2015 modernizing the ba role

10/5/15

1

Modernizing the BA Role

BA-Squared, LLC

Angela Wick, CBAP, PMP, PBA, ICP-ACC, ICP-BVA CEO & Founder of BA-Squared - www.BA-Squared.com

Trainer: •  BA-Squared Virtual Classroom •  BA-Squared Courses at Your Organization •  Univ. MN CCE BA & PM Instructor Consultant: •  Build BA Practices/CoEs •  Competency & Curriculum Development •  Agile Requirements Coach

•  Innovation Games Collaboration Architect •  IC Agile Certified Coach •  IC Agile Certified Business Value Analysis

Volunteer: •  PMI BA Practice Guide Expert Reviewer •  IIBA BABOK v3 Committee •  IIBA Competency Model Chair

@WickAng Angela@BA-‐Squared.com

10/5/15

2

Manic Monday

10/5/15

3

Copyright BA-Squared, LLC

10/5/15

4


How Did Business Analysis Happen in the Stone Age?


1700s - the 20th Century!

10/5/15

5


Later in the 20th Century

We worked really hard to put process and procedure into our problem solving domains. Systems and processes did not change oAen and things were rather predictable for periods of Cme


Year 2000ish and Web Exuberance

Our world starts to change VERY FAST!

10/5/15

6


21st Century

10/5/15

7


Tech Chaos – Value Lost?

Cynefin Model – Dave Snowden


Are We Trying To Manage The Complex with a Simple Mindset? •  Mini-Waterfall, Fragile, Scrumerfall

–  Smaller up front requirements –  Hand-offs à Lack of end to end analysis à Not following agile principles à Not seeing the results of agility in complex and complicated project environments and solutions

•  Delivery teams are agile, requirements are not à  Lack of collaboration to ensure we are building the right product. à  Not seeing the value benefits as value definition may be the complex/complicated part vs. delivery.

Results: We still have the same problem! Solutions not aligned to value, nor strategy and the wrong product is built perfectly right – sometimes….

10/5/15

8


Patterns in Requirements Agility


Vision

BA of the future!

10/5/15

9


•  GeXng out of your cube more to get others involved in models, diagrams and dialog

•  Create models and requirements informaCon together

START

•  PerfecCng models and documents at your desk and scheduling review meeCngs STOP

•  Leveraging your skills to see the whole and help other see the big picture CONTINUE

10/5/15

10


Modes of Technique Usage

TIME


Themes To Collaboration •  Huddles & Small Groups

•  Sticky Notes

•  Flip Charts & Whiteboards

•  Playing (Role Play, Acting, etc . . .)

•  Combination of individual thinking and group sharing in the same meeting

•  Other misc supplies (dot stickers, toys, play money)

10/5/15

11


Making Techniques Collaborative

•  Screen Mock Ups •  Scope Modeling •  Process Models •  Business Rules •  Decision Tables •  RACI Matrix •  Sequence Diagrams

•  Use Cases •  Functional Decomp •  Five Whys •  Prioritization •  Scenarios •  State Diagram •  User Stories & Maps

10/5/15

12


START • Embracing ambiguity • Discover what the ambiguity means

• Allowing requirements to evolve

STOP • ResisCng the urge to get to clarity right now on every requirement

CONTINE • To get to the details . . . When the feature has been ve`ed and is ready for more clarity vs. context

Use collaboraCon in your techniques to drive out the ambiguity and help the team discover and evolve their thoughts

10/5/15

13


•  Empathy Mapping •  Prototyping •  Card Sorting •  Mind Mapping •  Product/Vision Box •  Personas

• Using more user centered design techniques and collaboraCvely!

• Look at the system or product from the outside in

START

• Looking at systems from the inside out STOP

• Being an advocate for the user CONTINUE


START • Tracing to strategy, goals, objecCves, product vision, roadmap and prioriCes

STOP • Only thinking of traceability to test cases

CONTINE • To trace through the SDLC, but only at the level of detail that adds value

Agile project have this traceability built in when product vision, roadmaps, releases and iteraCons are all used and Ced together

10/5/15

14


How Do We Get There? •  Your value is NOT the

document – it’s the dialog and shared understanding YOU facilitate

•  Discovery and evolutionary mindset with requirements (vs. gathering)

•  Laser focus on value to the organization for each requirement and feature

10/5/15

15


BA of the future!

Call To Action! •  Ch Ch Ch Ch

Changes!

•  Keep learning!

•  Start Small

Twitter: @WickAng [email protected]