Welcome to 123ArticleOnline.com


Here's the recent articles submitted by mrugesh panchal

Articles By mrugesh panchal

Introduction About Basic Terms Of Scrum Tool   By: mrugesh panchal
Scrum Tool:- Scrum Tool is a Open source Project management tool with rich graphical interface for agile project development with scrum methodology that provides product backlog , Sprint management, Dashboard, Task board, Burndown chart and much more.(read entire article)
View : 431 Times
Category : Hardware/Software

Bharti Consulting Services Sarl, France Announces To Launch Open Source Scrum Tool By 31st November   By: mrugesh panchal
Bharti Consulting Services SARL, France announces to launch Open source scrum tool named as QuickScrum. Quickscrum Provides all functionalities related to scrum project management.. You will be able to download tool from our website or directly use it online (SaaS) at http://www.quickscrum.com.(read entire article)
View : 505 Times
Category : Computer Programming

An Overview Regarding Scrum Methodology   By: mrugesh panchal
For majority of the software developers, Agile methodology does not require any prior introduction. It is widely known that Agile is a comparatively new addition in the field of project management, and was primarily developed to overcome the drawbacks offered by traditional developmental methodologies such as the Waterfall method, which included a linear approach while executing projects. Typically, traditional methods support a top-to-bottom approach of segregating the entire project into main development activities, and tackling them one after another in a sequential method.(read entire article)
View : 457 Times
Category : General

True Meaning Of Scrum And Pitfalls To Avoid At All Costs    Submitted as:
It is highly common for many organization to revert to old Waterfall habits during the learning or early stages of Scrum. It is a serious pitfall, and project managers should refrain from falling into this habit if they are to get the maximum benefit out of scrum framework.(read entire article)
View : 332 Times
Category : General

In Scrum, Can A Sprint Be Cancelled? If So, When?    Submitted as:
Sprint is a very important part of scrum implementation, and its activity is carefully planned during the sprint planning meetings. In most cases, sprint process occurs as per plan, and a complete shippable product is delivered to the stakeholders and the product owner eventually. However, in rare circumstances, a sprint may be recalled or stopped due to various reasons.(read entire article)
View : 634 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 : 414 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 : 418 Times
Category : General

Understanding And Identifying Risks During Scrum Project Implementation - Avoid Potential Pitfalls    Submitted as:
Risks are an inherent part of any project, and for the project to be implemented in a successful manner, it is very important to identify the risks and cater to their solutions well in time to avoid any unpleasant or surprising situations. It is imperative to know about potential risks involved during scrum implementation.(read entire article)
View : 352 Times
Category : General

Is It Possible To Use Scrum For Developing Non It Based Projects? If So, How?    Submitted as:
It is important to look beyond IT development as far as scrum is concerned because there is a lot of potential in the framework. However, since scrum is all about adapting to changes, it becomes necessary to understand scrum in depth, and think positively how the methodology can be implemented for non-IT based projects.(read entire article)
View : 312 Times
Category : General

What Should The Perfect And Ideal Daily Stand-up Scrum Meeting Consist Of As Per The Official Scrum    Submitted as:
It is important to know what an ideal stand up or daily scrum meeting should consist of and what is to be discussed during the meeting. Scrum meetings play an important part in scrum methodology, and they should be properly understood so that effective and productive sprints can be planned and carried out.(read entire article)
View : 336 Times
Category : General