Skip to main content

SCRUM Meetings and it's importance


Scrum Meetings and it's importance

A large part of the SCRUM process revolves around the SCRUM Meetings and also User stories. User Stories are short description in non-technical language of how a system is expected to behave.
There are 4 meetings or ceremonies defined in the SCRUM framework. Each meetings happens at a specific time in each sprint and each has a set purpose and defines what participants are required and what artifacts are produced.

1.     Sprint Planning
This meeting happens before the sprint begins to define what will be delivered in the Sprint. Product owner, SCRUM Master and Scrum team, all are required in the sprint planning meeting.
In this meeting the top priority items are added to the product backlog and the priority of these items will be decided be Product Owner. Team breaks each backlog items into smaller tasks and estimates the work for each task. Once the team is filled with capacity for the sprint they stop taking new items and commit to completing the items in the backlog in next sprint.

2.     Daily Scrum Meetings
Also known as Scrum Standup meetings, is a short meeting for 15 minutes are less time duration among Scrum master and the Scrum team to share the status of the tasks they are working on.
Daily Scrum meeting is basically based on the 3 important question.
  •  What you did yesterday?
  • What are you going to do today?
  •  What is blocking your progress? 
Scrum meetings are not to solve issues that the team or individual is facing, it is only to make them visible to the other team members and to Scrum master.

3.     Sprint Review
Sprint review meeting is held at the completion of the sprint to demonstrate the product increment to customers and stakeholders. Product increment is a working software in a potentially shippable form. Product owner, SCRUM Master and Scrum team, all are required in the sprint review meetings. It should involve as many customers and stakeholders as possible to provide feedback on the working increment.

4.     Sprint Retrospective
Sprint Retrospective is held after the Sprint for the team to reflect and review, what went wrong in the last sprint and initiate process improvements.

5.     Backlog Grooming
Though not an official Scrum meeting, backlog grooming  is often held during the sprint to allow the team to assign a relative story point value to the top priority items in the product backlog. Scrum teams and product owners work together to clearly define the acceptance criteria for the work item.

Comments

Post a Comment

Popular posts from this blog

Get account Structure ranges set in AX Ledger

How to pass Account Structure ranges set in AX Ledger to an external system. Recently I have got a requirement where I have to populate same set of main account and financial dimension values to an external system using integration off course, which I have set in AX Ledger. The difficulty in this scenario was, how to get the valid set of main account and financial dimension values from AX.  Because AX gives us 'Segmented Entry Controls' where we just have to use the field as a segmented entry control and valid values will populate according to the Account Structure set in Ledger.  I have created a service class which extends "DimensionValueService" public class CMCDimensionValueService extends DimensionValueService {     // Insert list of valid main accounts to 'DimensionValueContract'     private void insertMainAccountValueLocalList(List                       _dimensionValueList,                                                  Dime
1 comment
Read more

Mass cheque printing in AX7/Dynamics 365 for finance & operation

AX7/Dynamics 365 for finance & operation: How to avoid user interaction while printing multiple cheques(Mass cheque printing) You all might be aware of the ‘Generate Payment’ functionality available in Dynamics AX. This function we use to generate/print cheques. The process is to create one payment journal, add few transactions with mode of payment as ‘Cheque’ then go for ‘Generate Payment’ option available in the drop down of ‘Function’ menu item button. Process is specific to print one cheque at a time for a single journal. Recently I came across a requirement where I had a customized form which contains multiple journal records and I have to add the ‘Generate Payment’ button on the form to allow user to print the checks for journals, and also allow user to select multiple journal records at the same time to print cheques and avoid user interaction with the system for each cheque. The major challenge here was, how to handle user interactions everytime to print multiple
Post a Comment
Read more

Hierarchy conflicts in AX 7 during migration from other AX versions and it's resolution - Delegates and Handlers

Delegates and Handlers in AX 7(Hierarchy conflicts resolution) Hi, We recently did a migration of our AX 2012 solution to AX 7, and while doing so one of the major challenge that we have faced are hierarchy conflicts. I'll be discussing here on the same. First of all we need to know that what is a hierarchy conflict. Coming to the AX 7 architecture, Application stack is divide into three basic packages. These are- 1: Application Platform 2: Application Foundation  3: Application Suite As shown in the above image, Application platform is the base package which contains Runtime and data access , work flow and services etc. and on top of it we have application foundation which contains organisation model, number sequence and GAB etc. and at the top we have Application Suite and Fleet Management. To understand the concept of these packages in depth you can follow the below link- Architecture changes in AX 7 All three models follows a hierarchy. Application p
Post a Comment
Read more