(Professional Business Analyst Training

organisation)

Overview of Scrum

Scrum

Scrum is approach or framework for developing software in incremental basis. Scrum is cross functional elf organizing team. Scrum follows fixed time period to complete task which are called sprints. Sprints can be max up to 4 weeks. In scrum large story EPIC is made to small parts which are called user stories.

RolesThere are 3 roles in scrumProduct owner-Person who has knowledge about all the requirements and lead the product vision which needs to be developed, and also who gives permission to ship the final product.Scrum Master-Who facilitates the smooth running of the scrum process.Scrum team-cross-functional and self organizing team who works on the user stories.

Meetings

Sprint Plan Meetings-Conducted at start of every spring and decides what they are developing and duration of sprint.Daily scrum meetings- Its daily standup meeting which scrum team attends discusses about the progress or status of work and are there any impediments that is slowing process. Its quick meeting max 15 minutes.

Traditional BA (Waterfall) Agile BA

Requirements are documented in Use Cases,Business Requirements, Functional requirements, UI Specifications, Business Rules.

Requirements are documented in Epics, User Stories and optionally Business (or Essential) Use cases.

   

Focuses on completeness of requirement and spends time in ensuring the requirement is unambiguous and has all the details.

Focuses on understanding the problem and being the domain expert so that s/he can answer questions from the development team swiftly and decisively.

Focuses on getting a ‘sign off’ on the requirements.

Focuses on ensuring the requirements meet the currentbusiness needs, even if it requires updating them.

Often there is a wall between the BA/Business and the Development team.

Agile BA (Often called as Product Owner) is part of the team.

Tends to dictate solutions.Has to remain in the problem domain, leaving the development team ‘space’ to explore different solutions.

Long turnaround. Quick turnaround.

Focus on what the requirements document said. In other words, output (Artifact) is a well written thorough requirements document.

Focus on the functionality of the developed software. In other words, output (Artifact) is the software that meets thebusiness needs.

   

Product backlog refinement-5-10% of sprint time is given for product back log refinement. Spring review meeting-Happens at end of the sprint, team shows the developed product to product owner and get it cleared, for a four week sprint review meeting can be max to 4 hours.Sprint retrospective meetings-this happens after completion of every sprint discuss about the positives and negatives about that sprint.

AgreementsProduct owner has two agreements1) Definition of ready2) Definition of done

Artifacts in scrumProduct Backlog, sprint Backlog, Release Burndown Sprint Burndown.