Intro to agile business analysis

IntroductionIntroductiontoto

Agile/ScrumAgile/Scrum& &

Agile Business AnalysisAgile Business Analysis

AgendaAgenda

►Overview of Agile and ScrumOverview of Agile and Scrum

►Scrum: SprintScrum: Sprint

►Agile Business AnalysisAgile Business Analysis

2

Overview of Agile and ScrumOverview of Agile and Scrum

Agile ManifestoAgile Manifesto

Agile software development is a set of Agile software development is a set of values:values: Individuals and interactionsIndividuals and interactions over processes over processes

and toolsand tools

Working softwareWorking software over comprehensive over comprehensive documentationdocumentation

Customer collaborationCustomer collaboration over contract over contract negotiationnegotiation

Responding to changeResponding to change over following a plan over following a plan3


Agile PrinciplesAgile Principles

►Highest priority is to satisfy the customerHighest priority is to satisfy the customerthrough early and continuous deliverythrough early and continuous deliveryof valuable softwareof valuable software

►Welcome changing requirementsWelcome changing requirements

►Deliver working software frequentlyDeliver working software frequently

►Business people and developers must Business people and developers must work work together daily throughout the projecttogether daily throughout the project

4


Agile Principles Agile Principles …cont’d…cont’d

►Build projects around motivated individualsBuild projects around motivated individuals

►The most efficient and effective method of The most efficient and effective method of conveying information is face-to-face conveying information is face-to-face conversationconversation

►Working software is the primary measure Working software is the primary measure of progressof progress

►Agile processes promote sustainable Agile processes promote sustainable developmentdevelopment

5


Agile Principles …cont’dAgile Principles …cont’d

►Continuous attention to technical Continuous attention to technical excellence excellence and good design enhances agilityand good design enhances agility

►Simplicity (art of maximizing amount Simplicity (art of maximizing amount of work not done) is essentialof work not done) is essential

►Best architectures, requirements, and Best architectures, requirements, and designs designs emerge from self-organizing teamsemerge from self-organizing teams

►At regular intervals, team reflects on how At regular intervals, team reflects on how to become more effective, then tunes and to become more effective, then tunes and adjustsadjusts

6


What is ScrumWhat is Scrum

► Scrum is an Agile framework that supports Scrum is an Agile framework that supports lightweight processes which emphasize:lightweight processes which emphasize: Incremental deliveriesIncremental deliveries Quality of ProductQuality of Product Continuous improvementContinuous improvement Discovery of people’s potentialDiscovery of people’s potential

► Scrum is simple to understand, but requires Scrum is simple to understand, but requires discipline in order to be successfuldiscipline in order to be successful

► Scrum is not a methodologyScrum is not a methodology

7

Overview of Agile and ScrumOverview of Agile and Scrum Foundations of ScrumFoundations of Scrum

► Empiricism Empiricism Detailed up-front planning and defined processes are Detailed up-front planning and defined processes are

replaced by just-in-time Inspect and Adapt cyclesreplaced by just-in-time Inspect and Adapt cycles► Self-OrganizationSelf-Organization

Small teams manage their own workload and organize Small teams manage their own workload and organize themselves around themselves around clear goals and constraintsclear goals and constraints

► PrioritizationPrioritization Do the next right thingDo the next right thing

► RhythmRhythm Allows teams to avoid daily noise and focus on deliveryAllows teams to avoid daily noise and focus on delivery

► CollaborationCollaboration Leaders and customers work with the Team, rather than Leaders and customers work with the Team, rather than

directing themdirecting them

8

Overview of Agile and ScrumOverview of Agile and Scrum Core ValuesCore Values

► TransparencyTransparency Everything about a project is visible to everyoneEverything about a project is visible to everyone

► CommitmentCommitment Be willing to commit to a goalBe willing to commit to a goal

► CourageCourage Have the courage to commit, to act, to be open and to Have the courage to commit, to act, to be open and to

expect respectexpect respect► FocusFocus

Focus all of your efforts and skills on doing the work Focus all of your efforts and skills on doing the work that you have committed to doingthat you have committed to doing

► RespectRespect Respect and trust the different people who comprise a Respect and trust the different people who comprise a

teamteam9

Scrum: SprintScrum: Sprint


Role: ScrumMasterRole: ScrumMaster

►Servant LeaderServant Leader

►Facilitates the ProcessFacilitates the Process

►Supports the TeamSupports the Team

►Removes Organizational ImpedimentsRemoves Organizational Impediments

►Socializes Scrum to ManagementSocializes Scrum to Management

►Enable close collaboration across all Enable close collaboration across all roles and functionsroles and functions

11


Role: TeamRole: Team

►Cross-Functional Cross-Functional

►5-9 Members5-9 Members

►Self-OrganizingSelf-Organizing

►Focused on meeting CommitmentsFocused on meeting Commitments

12


Role: RelationshipsRole: Relationships

13

Scrum DiagramScrum Diagram

14


Flow & Artifacts: PlanningFlow & Artifacts: Planning

►Sprint Planning meeting held at beginning of each Sprint Planning meeting held at beginning of each SprintSprint

►Time and Resources are fixed in any given Sprint Time and Resources are fixed in any given Sprint

►Goal is to have prioritized Sprint Backlog, broken Goal is to have prioritized Sprint Backlog, broken down into tasks, that the Team can commit todown into tasks, that the Team can commit to

►During planning, Team commits to scope that can During planning, Team commits to scope that can be completed in the Sprint, taking into account the be completed in the Sprint, taking into account the definition of Donedefinition of Done

►Story points may be refinedStory points may be refined

15


Flow & Artifacts: Daily StandupFlow & Artifacts: Daily Standup

►Meetings held in same location, same Meetings held in same location, same time, every daytime, every day

►Typically of 15 minutesTypically of 15 minutes►Encourages Encourages self-organization,self-organization, rhythm,rhythm, and and

collaborationcollaboration►NotNot a status meeting a status meeting►Each Team member speaks to:Each Team member speaks to:

What I did yesterdayWhat I did yesterday What I plan to do todayWhat I plan to do today Any roadblocks in the way of my workAny roadblocks in the way of my work

16


Flow & Artifacts: Sprint ReviewFlow & Artifacts: Sprint Review

►Occurs at the end of each SprintOccurs at the end of each Sprint

► Inspect and Adapt the Inspect and Adapt the productproduct

►The team meets with the Product Owner The team meets with the Product Owner (and Stakeholders) to demonstrate the (and Stakeholders) to demonstrate the working software from the Sprintworking software from the Sprint

►This is a hands-on software demo (not a This is a hands-on software demo (not a PowerPoint) that usually requires some PowerPoint) that usually requires some prep beforehandprep beforehand

17


Flow & Artifacts: RetrospectiveFlow & Artifacts: Retrospective

►Occurs at the end of each SprintOccurs at the end of each Sprint

► Inspect and Adapt the Inspect and Adapt the processprocess

►Team and ScrumMaster meet to reflect on Team and ScrumMaster meet to reflect on what went well and what can be improvedwhat went well and what can be improved

►Tone of the meeting is that everyone did Tone of the meeting is that everyone did their best and now look to how can we their best and now look to how can we improveimprove

►Retrospectives must conclude with team Retrospectives must conclude with team commitments to actioncommitments to action

18

What is in it for me? (Customer)What is in it for me? (Customer)

►As a customer , I want to be able toAs a customer , I want to be able to Have Opportunity to provide Have Opportunity to provide

feedback earlyfeedback early Go to market faster with QualityGo to market faster with Quality Faster return on investmentFaster return on investment

19

What is in it for me? (Leadership)What is in it for me? (Leadership)

►As a Leader , I wantAs a Leader , I want To understand progress in terms To understand progress in terms

of real progress made on of real progress made on product . product .

Better engaged & accountable Better engaged & accountable team team

20

What is in it for me? ( Team Member)What is in it for me? ( Team Member)

►Who is a typical team member?Who is a typical team member?►As a team member, I wantAs a team member, I want

A sustainable paceA sustainable pace Satisfaction of quality product Satisfaction of quality product

delivereddelivered Clear Priority and less Clear Priority and less

interruption during developmentinterruption during development

21

How do you learn Scrum – By Doing?How do you learn Scrum – By Doing?

►Apply few practices at a timeApply few practices at a time►Understand the values and Understand the values and

foundationsfoundations►Inspect and AdaptInspect and Adapt►Experience the Joy of Doing Experience the Joy of Doing

ScrumScrum

22

Agile Business AnalysisAgile Business Analysis

Agile Business Analysis

Agile business analysis frameworks

►The discovery framework,The discovery framework,►The delivery frameworkThe delivery framework

24


The discovery frameworkThe discovery framework

►See The Whole,►Think as a Customer,Think as a Customer,►Analyze to Determine What is ValuableAnalyze to Determine What is Valuable

25


The delivery frameworkThe delivery framework

►Get Real Using Examples,►Understand What is Doable,Understand What is Doable,►Stimulate Collaboration and Stimulate Collaboration and

Continuous Improvement,Continuous Improvement,►Avoid WasteAvoid Waste

26


Principles of Agile Business Principles of Agile Business AnalysisAnalysis

27

Questions?Questions?

28

References:References:

1. 1. Agile Manifesto - http://agilemanifesto.org/principles.htmlAgile Manifesto - http://agilemanifesto.org/principles.html

2. The Agile Extension to the BABOK- Guide2. The Agile Extension to the BABOK- Guide

Prepared by: Sumit MahajanPrepared by: Sumit Mahajan

29

Intro to agile business analysis

Technology

agile business

team member

sprintflow

agile

team

understand

sprint

commit