Top Banner

Click here to load reader

Intro to agile business analysis

Oct 19, 2014

ReportDownload

Technology

This presentation covers the basics of agile software development and intro to agile business analysis frameworks.

Scrum 101

IntroductiontoAgile/Scrum& Agile Business Analysis

AgendaOverview of Agile and Scrum

Scrum: Sprint

Agile Business Analysis

*

Overview of Agile and ScrumAgile ManifestoAgile software development is a set of values:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan*

Overview of Agile and ScrumAgile PrinciplesHighest priority is to satisfy the customer through early and continuous delivery of valuable softwareWelcome changing requirementsDeliver working software frequentlyBusiness people and developers must work together daily throughout the project*

Overview of Agile and ScrumAgile Principles contdBuild projects around motivated individualsThe most efficient and effective method of conveying information is face-to-face conversationWorking software is the primary measure of progressAgile processes promote sustainable development*

Overview of Agile and ScrumAgile Principles contdContinuous attention to technical excellence and good design enhances agilitySimplicity (art of maximizing amount of work not done) is essentialBest architectures, requirements, and designs emerge from self-organizing teamsAt regular intervals, team reflects on how to become more effective, then tunes and adjusts

*

Overview of Agile and ScrumWhat is ScrumScrum is an Agile framework that supports lightweight processes which emphasize:Incremental deliveriesQuality of ProductContinuous improvementDiscovery of peoples potentialScrum is simple to understand, but requires discipline in order to be successfulScrum is not a methodology

*

Overview of Agile and Scrum Foundations of ScrumEmpiricism Detailed up-front planning and defined processes are replaced by just-in-time Inspect and Adapt cyclesSelf-OrganizationSmall teams manage their own workload and organize themselves around clear goals and constraintsPrioritizationDo the next right thingRhythmAllows teams to avoid daily noise and focus on deliveryCollaborationLeaders and customers work with the Team, rather than directing them*

Overview of Agile and Scrum Core ValuesTransparencyEverything about a project is visible to everyoneCommitmentBe willing to commit to a goalCourageHave the courage to commit, to act, to be open and to expect respectFocusFocus all of your efforts and skills on doing the work that you have committed to doingRespectRespect and trust the different people who comprise a team*

Scrum: Sprint

Scrum: SprintRole: ScrumMasterServant LeaderFacilitates the ProcessSupports the TeamRemoves Organizational ImpedimentsSocializes Scrum to ManagementEnable close collaboration across all roles and functions

*

Scrum: SprintRole: TeamCross-Functional 5-9 MembersSelf-OrganizingFocused on meeting Commitments*

Scrum: SprintRole: Relationships*

Scrum Diagram*

Scrum: SprintFlow & Artifacts: PlanningSprint Planning meeting held at beginning of each SprintTime and Resources are fixed in any given Sprint Goal is to have prioritized Sprint Backlog, broken down into tasks, that the Team can commit toDuring planning, Team commits to scope that can be completed in the Sprint, taking into account the definition of DoneStory points may be refined*

Scrum: SprintFlow & Artifacts: Daily StandupMeetings held in same location, same time, every dayTypically of 15 minutesEncourages self-organization, rhythm, and collaborationNot a status meetingEach Team member speaks to:What I did yesterdayWhat I plan to do todayAny roadblocks in the way of my work*

Scrum: SprintFlow & Artifacts: Sprint ReviewOccurs at the end of each SprintInspect and Adapt the product The team meets with the Product Owner (and Stakeholders) to demonstrate the working software from the SprintThis is a hands-on software demo (not a PowerPoint) that usually requires some prep beforehand

*

Scrum: SprintFlow & Artifacts: RetrospectiveOccurs at the end of each SprintInspect and Adapt the processTeam and ScrumMaster meet to reflect on what went well and what can be improvedTone of the meeting is that everyone did their best and now look to how can we improveRetrospectives must conclude with team commitments to action*

What is in it for me? (Customer)As a customer , I want to be able toHave Opportunity to provide feedback earlyGo to market faster with QualityFaster return on investment

*

What is in it for me? (Leadership)As a Leader , I wantTo understand progress in terms of real progress made on product . Better engaged & accountable team

*

What is in it for me? ( Team Member)Who is a typical team member?As a team member, I wantA sustainable paceSatisfaction of quality product deliveredClear Priority and less interruption during development

*

How do you learn Scrum By Doing?Apply few practices at a timeUnderstand the values and foundationsInspect and AdaptExperience the Joy of Doing Scrum

*

Agile Business Analysis

Agile Business AnalysisAgile business analysis frameworks The discovery framework,The delivery framework

*

Agile Business AnalysisThe discovery framework

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

*

Agile Business AnalysisThe delivery framework

Get Real Using Examples,Understand What is Doable,Stimulate Collaboration and Continuous Improvement,Avoid Waste

*

Agile Business AnalysisPrinciples of Agile Business Analysis

*

Questions?*

References:

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

2. The Agile Extension to the BABOK- Guide

Prepared by: Sumit Mahajan

*

Test

********Doing Scrum mechanics without these values misses the point. These values are not unique to Scrum, but the Scrum Framework is built on top of these values.***Cross-Functional = Dev, QA, Bus Analyst, UI Designer, Architect**done in two meetings. Requirements Workshop and Design WorkshopCan also have Pre-Planning (Estimation) and Product Backlog Grooming meetingIf commitment is inaccurate (either under-commit or over-commit), then stories are to be added or removed. Team would then reflect in the Retrospective and accordingly adjust their upcoming commitments*****