Agile SCRUM Model (Professional Business Analyst Training organisation)
There is no particular definition for scrum... Agile SCRUM Model is just one of the many iterative and incremental agile software development projects and product or application development. So Scrum is actually a type of Agile approach which is used commonly in software developments.
So, Scrum is a specific essence of Agile, specifically it is referred to as an agile project management framework. Scrum has mainly two roles: •
Main/Core Role
•
Ancillary Role
Main/Core role: It consists of... Scrum Master Product Owner â—?
Development Team
Traditional BA (Waterfall)
Agile BA
Requirements are documented in Use Cases, Requirements are documented in Epics, User Business Requirements, Functional requirements, Stories and optionally Business (or Essential) Use UI Specifications, Business Rules. 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 ensuring the requirements meet the Focuses on getting a ‘sign off’ on the requirements. currentbusiness needs, even if it requires updating them. Often there is a wall between the BA/Business and Agile BA (Often called as Product Owner) is part of the Development team. the team. Tends to dictate solutions. Long turnaround.
Has to remain in the problem domain, leaving the development team ‘space’ to explore different solutions. Quick turnaround.
Focus on what the requirements document said. In Focus on the functionality of the developed other words, output (Artifact) is a well written software. In other words, output (Artifact) is the thorough requirements document. software that meets thebusiness needs.
Scrum Masters: It ensure this process happens as smoothly as possible, and continually help improve the process, the team and the product being created. Product Owners: It determines what needs to be built in the next 30 days or less.
Development Teams: Build what is needed in 30 days (or less), and then demonstrate what they have built. Base on this demonstration, the Product Owner determine what to build next. Ancillary Role: The ancillary roles in Scrum teams are those with no formal role and infrequent involvement in the Scrum processing but nevertheless, they must be taken into account. Stakeholders, Managers.
Scrum Master:- There are few types of meetings in scrum: Daily Scrum: • Standup Backlog grooming • Story time Scrum of Scrums • Sprint planning meeting • Sprint review meeting • Sprint retrospective
What is Sprint? In the SCRUM methodology a sprint is the basic unit of progress. Each sprint is preceded by a planning meeting, where the everyday jobs for the sprint are identified and an expected commitment for the sprint goal is made.
In the Agile methods every iteration involves a team working through a full software development cycle, including planning, requirements analysis, design, coding, unit testing, and acceptance testing when a working product is demonstrated to stakeholders.
In a “SCRUM” sprint you execute all the software development phases (from requirement analysis to acceptance testing), and in my opinion you should, you can say SCRUM sprints correspond to AGILE iterations.