Welcome to 123ArticleOnline.com


Here's the recent articles submitted by mrugesh panchal

Articles By mrugesh panchal

How To Determine The Ideal Sprint Duration Or Length? Which Factors Should Be Considered To Benefit   By: mrugesh panchal
Many organizations have their own particular thoughts and beliefs regarding what the ideal sprint duration ought to be. It is worthwhile knowing about certain key factors which generally affect, and also determine, the actual sprint durations set up by the scrum team.(read entire article)
View : 453 Times
Category : Hardware/Software

Basic Objectives Of The Sprint Review Meeting In Scrum   By: mrugesh panchal
A sprint review meeting is held just after a sprint ends. The meeting usually lasts for four to eight hours. The duration of the sprint has a lot to do with how long the sprint review lasts, and its time is determined on the basis of the sprint duration. The most significant part of the sprint review is to demonstrate the user stories developed by the team during the daily sprints. Ideally, the team should not invest more than an hour in show casing their sprint activity to the product owner, since time is required to carry out other review related activities by the scrum team. In most cases, the review is held on the last day of the sprint, or the day immediately succeeding it, if it is a working day. The main purpose of the meeting is to exhibit the tasks to the product owner and the scrum master. The scrum master plays a passive role during the review, and is primarily responsible for facilitating the meeting rather than taking an active part in it. The product owner reviews the user stories developed during the sprint iteration, and verifies whether the product backlog items are developed in a manner such that they satisfy the acceptance criteria defined by the product owner when the product backlog is created by him or her during the project inception. Primary objectives of a sprint review meeting The objective of the review is to: • Display the work carried out during the sprint to the product owner. • Have the user stories accepted as “done” provided they fulfill the acceptance criteria. • Adjudge whether the development team has delivered work as per commitment. • Determine whether the tasks have been developed as per instructions given to the team members during the sprint planning meeting. • Find whether the team faced any problems while the sprint was underway. If so, what were they? • Support the self-learning feature of scrum and find what lessons can be learnt from the sprint just carried out. • Estimate the velocity of work carried out by the team during the sprint. • Decide how to proceed with the next sprint. Most of the times, Agile teams will ask the stakeholders to accept the work as “done” if the development satisfies the acceptance criteria, and the product owner gives the “green” signal. If the user stories are “shippable”, there is no reason why the investors and stakeholders should delay in accepting them as final and done. Even though there is an entirely separate meeting – the sprint retrospective meeting – to carry out the same activity, the basic intention is to save time during the retrospective, and utilize the “extra” time to discuss issues that are more important. Each event in scrum is time boxed. The team is always pressed for time, and tries to take the maximum benefit of available time.(read entire article)
View : 483 Times
Category : Hardware/Software

What Is Velocity And Its Importance In Scrum Methodology?   By: mrugesh panchal
Velocity and burn down charts play an important part in scrum. Right from creating the project estimation, velocity is used by the scrum team to enhance and improve scrum implementation through the self-correction and self-learning features supported by scrum.(read entire article)
View : 537 Times
Category : Hardware/Software

Importance Of "done" In Scrum And Why Acceptance Criteria Is So Important   By: mrugesh panchal
The fulfillment of the acceptance criteria linked with the product backlog items, or accepting the user stories as “done” is very important in scrum. When shippable stories are developed through the sprints on a regular and consistent basis the ROI and the profit margins increase. It is important to know why “done” is so important for scrum methodology.(read entire article)
View : 571 Times
Category : Hardware/Software

Writing Effective And Useful User Stories – How To Reduce Regression In Scrum   By: mrugesh panchal
In scrum, the success of delivering shippable user stories depend a lot upon the manner and way in which the product backlog items are defined and stated. It is very important to write useful and easily understandable acceptance criteria and link it to the stories. The team can deliver successful stories only if the criterion is made clear and explained to the team. A useful rule can help the product owner draft effective user stories.(read entire article)
View : 498 Times
Category : Hardware/Software

Product Backlog Grooming Issues And What Should An Ideal Grooming Session Include?   By: mrugesh panchal
Properly groomed product backlogs can help to streamline the scrum process and help to deliver shippable user stories having high business values. Lack of proper grooming can lead to several issues and reduced profit margins for the investors. Proper grooming should be carried out using the DEEP method so fruitful product increment can be availed from the scrum project.(read entire article)
View : 433 Times
Category : Hardware/Software

Breathing New Life Into The Sprint Retrospective Meetings – Part 1   By: mrugesh panchal
Sprint retrospective meetings are important events in scrum. The scrum master should ensure the retrospectives are conducted in the correct spirit and manner so that they can remain effective. If the retrospectives are “dying” out i.e. they no longer remain effective, new life can be breathed into them by implementing certain recommendations.(read entire article)
View : 510 Times
Category : Hardware/Software

In Scrum, Can The Development Team Decide What Is "done"? If So, Why?   By: mrugesh panchal
The acceptance criteria is very important in defining which of the user stories can be considered as “done” at the end of the sprint. Scrum advocates shippable user stories to be delivered at the end of each sprint iteration. The definition of “done” decides whether a particular product backlog item is shippable or not after it is developed. Apart from the stakeholders, can the team decide the acceptance criteria and decide what is “done” in scrum?(read entire article)
View : 419 Times
Category : Hardware/Software

How Can A Product Owner Decide Which User Stories Should Be Defined In A Product Backlog?   By: mrugesh panchal
The product owner should define correct user stories in scrum if the project is to be successful. Certain questions can help the PO ascertain whether an item should be developed as a user story or not.(read entire article)
View : 454 Times
Category : Hardware/Software

Using Shared Resources In Daily Sprints - How Is This Possible In Scrum?   By: mrugesh panchal
Scrum management and product owners may decide to share the resources for a number of reasons. It is worth knowing about two common scenarios in which resources sharing occurs.(read entire article)
View : 517 Times
Category : Hardware/Software