Agile business analyst

THE AGILE BUSINESS ANALYST Present  b y  :  John  Doan  (Đoàn  Đức  Đề) Source:  Some  from  Internet @APEX  Global  Corporation Info@apexglobal.com.vn Agenda v IIBA’s Business Analysis Core Concept Model (BACCM) v The Business Analysis Body of Knowledge® Version v What is Agile Method? v Waterfall and Agile project success rates v The Agile Business Analysis Body Of Knowledge v Difference in Working styles v Agile Requirements @APEX  Global  Corporation Info@apexglobal.com.vn The Business Analysis Core Concept ModelTM -BACCM v What is the kind of change we're doing? v What are the needs we're trying to satisfy? v What are the solutions we're creating or changing? v Who are the stakeholders involved? v What stakeholders consider to be of value? v What is the context that we and the solution are in? @APEX  Global  Corporation Changes Solutions Needs BABOK3 Stake holders Info@apexglobal.com.vn Contexts Value The Business Analysis Body Of Knowledge® Version The  Information   Technology Elicitation  and   Collaboration   Business   Analysis   Planning  and   Monitoring   Requirements   Life  Cycle   Management   BABOK3 Strategy   Analysis   The  Agile   Perspective The  Business   Architecture Solution   Evaluation   Requirements   Analysis  and   Design   Definition   Underlying  Competencies   @APEX  Global  Corporation Info@apexglobal.com.vn The  Business   Intelligence The  Business   Process   Management What are problems of Product/System? @APEX  Global  Corporation Info@apexglobal.com.vn What is Agile Method? We  are  uncovering  better  ways  of  developing  software  by  doing  it   and  helping  others  do  it   Through  this  work  we  have  come  to  value: Agile  Benefits   •   Higher   productivity   and  lower  cost   •   Improved   employee  engagement   and  job   satisfaction   •   Faster  time  to  market   •   Higher   quality   •   Improved   stakeholder  satisfaction   @APEX  Global  Corporation Info@apexglobal.com.vn Waterfall and Agile project success rates Agile   projects  are  successful  three  times  more  o  en than   non-­‐agile   projects,  according  to  the  2012   CHAOS  Manifesto  Report  from  the  S tandish  Group   @APEX  Global  Corporation Info@apexglobal.com.vn Introduction to SCRUM Framework SPRINT NO  CHANGE in  D uration   or   Goal @APEX  Global  Corporation Info@apexglobal.com.vn The Agile BABOK - Strategy Analysis v Work with the customer to develop strategic goals and a product vision v Identifying the “value stream” for the proposed product v Brokering effective information exchange between the customer and the IT team v The correct scope for Agile projects isn’t defined requirements, but the well articulated product vision @APEX  Global  Corporation Info@apexglobal.com.vn The Agile BABOK - Business Analysis Planning and Monitoring 10 v Requirements evolve with greater product exposure v A lean principle: just enough, just in time v Requirements are planned for delivery in time-boxed iterations v BA’s help to negotiate standards and the specifics of product requirements @APEX  Global  Corporation Info@apexglobal.com.vn The Agile BABOK - Elicitation and Collaboration 11 v Understanding the customer’s needs is essential v Who are your customers? v How will your customer use your product? v What are your customers priorities? v User Stories capture requirements using the following form: As a , I want , so that @APEX  Global  Corporation Info@apexglobal.com.vn The Agile BABOK - Requirements Life Cycle Management 12 Top Stories for the Sprint Planning Fibonacci Number Series 1,2,3,5,8,13,21,34 STORY  (5) STORY   (8) STORY  (13) STORY  (13),  STORY  (13) STORY   (21),    STORY   (21)   STORY  (34),                STORY  (34)   STORY,                STORY,                STORY STORY,                    STORY,                    STORY EPIC,                                      EPIC,                                      EPIC EPIC @APEX  Global  Corporation Info@apexglobal.com.vn Highest Business Value Highest Priority Small Stories Testable Stories No Dependencies Sized Stories The Agile BABOK - Requirements Analysis and Design Definition 13 v Understanding “the why” can be as important as “the what” As  an  speaker,  I  want  to   make  my  presentation   available  to  attendees   online,  so  that  I  do  not  need   to  send  it   @APEX  Global  Corporation As  an  attendee,  I  want  to   download  the   presentation,  so  that I  share  what  I  have   learned   Info@apexglobal.com.vn Portfolio Investment Themes Epics Program Feature Story Team Task @APEX  Global  Corporation Info@apexglobal.com.vn The Agile BABOK - Solution Evaluation 15 v Delivering the solution in small bites v Reviewing requirements during planning v Reviewing requirements during demo v Requirements describe solution to business needs v Determining requirements as late as possible v Validating requirements through prioritizing delivery @APEX  Global  Corporation Info@apexglobal.com.vn Difference in Working styles 16 Traditional  BA   Agile  BA Focus Requirements  Documentation   Value  Delivery  in  the  form  of   Business  Outcomes Artifacts Requirement  Documents Backlogs Requirements  Definition   All  requirements   defined   upfront Defined   continuously   in  small   batches  (i.e.,  Features) Requirements  Writing   Written  by  BA Written  by  anyone  and   collaboratively  elaborated Requirements  Format   “Shall”  Statements   User  Stories   Negotiability Non-­‐negotiable Negotiable Sign-­‐Offs   Formal  Sign-­‐Off   obtained   Quick  feedback   Requirement  Changes   Strictly  controlled  after   baseline Changes  are  anticipated  and   welcome  at  any  time   Location Usually  separate  from  the   development   team Often  collocated  and  part  of   the  development   team   @APEX  Global  Corporation Info@apexglobal.com.vn Agile Requirements 17 v Requirements are defined iteratively and incrementally v Requirements are maintained in backlogs, not in paper v Requirements not go through a formal sign-off process v Solution requirements are defined via conversations between the team and users v Business analysis work is done in increments rather than all up-front v More emphasis is placed on verbal and visual communications versus paper documents v Just enough, just-in-time v Requirements are collaborative @APEX  Global  Corporation Info@apexglobal.com.vn Q&A @APEX  Global  Corporation Info@apexglobal.com.vn [...]...The Agile BABOK - Elicitation and Collaboration 11 v Understanding the customer’s needs is essential v Who are your customers? v How will your customer use your product? v What are your customers priorities? v User Stories capture requirements using the following form: As a , I want , so that @APEX  Global  Corporation Info@apexglobal.com.vn The Agile. .. EPIC,                                      EPIC,                                      EPIC EPIC @APEX  Global  Corporation Info@apexglobal.com.vn Highest Business Value Highest Priority Small Stories Testable Stories No Dependencies Sized Stories The Agile BABOK - Requirements Analysis and Design Definition 13 v Understanding “the why” can be as important as “the what” As  an  speaker,  I  want  to... Investment Themes Epics Program Feature Story Team Task @APEX  Global  Corporation Info@apexglobal.com.vn The Agile BABOK - Solution Evaluation 15 v Delivering the solution in small bites v Reviewing requirements during planning v Reviewing requirements during demo v Requirements describe solution to business needs v Determining requirements as late as possible v Validating requirements through prioritizing... possible v Validating requirements through prioritizing delivery @APEX  Global  Corporation Info@apexglobal.com.vn Difference in Working styles 16 Traditional  BA   Agile  BA Focus Requirements  Documentation   Value  Delivery  in  the  form  of   Business  Outcomes Artifacts Requirement  Documents Backlogs Requirements  Definition   All  requirements   defined   upfront Defined   continuously   in  small...   team   @APEX  Global  Corporation Info@apexglobal.com.vn Agile Requirements 17 v Requirements are defined iteratively and incrementally v Requirements are maintained in backlogs, not in paper v Requirements do not go through a formal sign-off process v Solution requirements are defined via conversations between the team and users v Business analysis work is done in increments rather than all