123ArticleOnline Logo
Welcome to 123ArticleOnline.com

Here's the recent articles submitted by mrugesh panchal

Articles By mrugesh panchal

Page: << <    1 [2]  3  4  5    > >>

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 : 220 Times
Category : Hardware/Software

Can A Scrum Project Have Multiple Product Owners Or Scrum Masters?   By: mrugesh panchal
Scrum advocates each team should have only one scrum master and a single product owner. In real life, it is possible to have more than one product owner and multiple scrum masters for a single project? Is this possible? Find out how.(read entire article)
View : 278 Times
Category : Hardware/Software

Discover What Is Scrum Methodology And How It Works    Submitted as:
Scrum methodology has a lot to offer in terms of flexibility and adapting to changing user requirements. Having an overview or a rough idea can help you know what advantages scrum has to offer, and how you can benefit by them.(read entire article)
View : 184 Times
Category : General

Dual Roles Of A Product Owner – The Stakeholders And The Team, How To Balance Them?   By: mrugesh panchal
The product owner is very important for the scrum project, and his or her role is a difficult one to play. The person acting in the capacity of a product owner has to balance the stakeholders and the end users on one hand, and the scrum team on the other. It is worth knowing how one can possibly do it.(read entire article)
View : 190 Times
Category : Hardware/Software

Effective And Productive Features Of A Scrum Retrospective Meeting - What Every Scrum Person Should    Submitted as:
Scrum retrospective meetings are important as they help to disclose the pitfalls with scrum implementation. It is important to hold the meetings in then correct manner and spirit to get the most out of the discussions carried out during the retrospective.(read entire article)
View : 186 Times
Category : General

Effective And Productive Features Of A Scrum Retrospective Meeting – What Every Scrum Person Should   By: mrugesh panchal
Sprint retrospectives are a technique in Scrum, used primarily to reveal or disclose the shortcomings and behavior of the scrum team to itself. When it becomes possible for a self-organizing body or a system to correctly identify the pitfalls and problems faced by it, it is possible to correct them by implementing proper solutions which can eradicate the impediments and remove the problematic issues from its roots. During scrum implementation, sprint retrospectives help to identify any erroneous working or problems faced by the team, and efforts are made to correct the problems in time. For retrospectives to be meaningful and useful, more emphasis should be stressed upon self-reflection – each member of the team should feel personally involved and responsible for the outcomes derived out of the sprint activity. This is one of the main essences of scrum. In addition to collaboration and team effort, scrum framework strongly promotes self-analysis and self-correction. Sprint retrospectives help to incorporate these scrum features during the implementation stage. Features of a healthy and beneficial sprint retrospective The scrum guide has little to say about what an ideal retrospective should consist of. Since scrum is all about adapting to changes and collaboration of activities, it can be very difficult to specify exactly what the retrospective should include. Business processes can vary, and scrum implementation may be carried out in a customized manner to suit the particular organization or business. In short, it may be very difficult to define and standardize a retrospective. Rather, it would prove to be more meaningful and effective if the objectives and results of the retrospective are to be considered, instead of its anatomy or structure. Teams may vary, and can be big or small in size. The location should be ideally fixed, but it too can change as per convenience and feasibility. What does not change are the objective for which the retrospective is to be held, and what results are to be obtained out of it. Ideally, a sprint retrospective should support the following features: • Each team member should engage in the discussion and actively support it in a pro-active manner. • Discussions carried out ought to focus upon team activity and teamwork rather than individual team members. • The definition of “Done” is clearly defined and explained properly to team members. Completed user stories should be accepted as “Over” or “Complete” only on the basis of the definition of “Done”. • A list of all actionable commitments should be created. • The results of prior retrospectives are thought about and analyzed from time to time. • Only relevant discussion pertaining to scrum implementation should be carried out. Who attends the sprint retrospective? Everybody associated with the scrum project and scrum implementation should attend the retrospective. This includes the product owner and all team members. The scrum master too attends the meeting, but rather than indulging in active discussion, he or she engages in a manner which can facilitate the meeting, and positive results are derived out of it. Supporting the correct spirit while holding the retrospective Regardless about who attends the meeting, or the level of seniority, there should be active participation by all the attendees, and discussions should be carried out in an open manner with a clear view of finding true and genuine solutions, rather than finding faults of individuals. Of course, self-introspection and error finding is a must as far as scrum is concerned, but instead of targeting specific individuals, it is important to discuss about team as a whole, and find solutions collectively.(read entire article)
View : 198 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 : 194 Times
Category : Hardware/Software

How Should Items Be Arranged In A Product Backlog?   By: mrugesh panchal
The product backlog forms the backbone of all activities carried out while implementing scrum methodology, and it should be carefully created by the product owner. It is important to know what the product backlog includes and how the user stories should be arranged in it before proceeding with additional scrum related topics.(read entire article)
View : 949 Times
Category : Hardware/Software

How Sprint Reviews Are Different From Sprint Retrospectives In Scrum?   By: mrugesh panchal
Both the sprint review meeting and the sprint retrospective meeting are important scrum ceremonies. They have their own particular importance in scrum methodology. It is important not to get confused between the two events. Find how they are different from each other.(read entire article)
View : 190 Times
Category : Hardware/Software

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 : 200 Times
Category : Hardware/Software

See As RSS
Login To Account
Login Email:
Forgot Password?
New User?
Sign Up Newsletter
Email Address: