We normally do not associate companies in the private sector with bureaucracy and reserve that criticism mostly for governments and public sector organizations. But how many times have we waited for a response from a department which never came? How many times have we felt things have taken twice as long as they should have?…
Request for changes are usually submitted as Change Requests. Change Requests remain unapproved until they get formally approved. The Scrum Guidance Body usually defines a process for approving and managing changes throughout the organization. In the absence of a formal process, it is recommended that small changes that do not have a significant impact on…
Scrum principles are the foundation on which the Scrum framework is based. The principles of Scrum can be applied to any type of project or organization, and they must be adhered to in order to ensure appropriate application of Scrum. The aspects and processes of Scrum can be modified to meet the requirements of the…
Does accepting greater responsibility mean delivering greater value? Scrum believes that employees are self-motivated and seek to accept greater responsibility. So, they deliver much greater value when self-organized. The preferred leadership style in Scrum is “servant leadership”, which emphasizes achieving results by focusing on the needs of the Scrum Team. Benefits of Self-Organization Self-organization as…
In Scrum, all requirements related to an ongoing Sprint are frozen during the Sprint. No change is introduced until the Sprint ends, unless a change is deemed to be significant enough to stop the Sprint. In the case of an urgent change, the Sprint is terminated and the team meets to plan a new Sprint.…
Done Criteria are a set of rules that are applicable to all User Stories in a given Sprint. General Done Criteria could include any of the following: Reviewed by other team members Completed unit testing of the User Story Completion of quality assurance tests Completion of all documentation related to the User Story All issues…
The Scrum Master is the “servant leader” of the Scrum Team who moderates and facilitates team interactions as team coach and motivator. The Scrum Master is responsible for ensuring that the team has a productive work environment by guarding the team against external influences, removing any obstacles, and enforcing Scrum principles, aspects, and processes. Different…
Impediment Log: is an important tool in which all the impediments affecting the project are documented. An Impediment is usually described as an obstacle, hindrance or hurdle which can decrease the productivity and performance of the Scrum team. It is mandatory that they should be identified as soon as possible, solution found in quick time…
Probably this is one of the most frequently asked questions in relation to implementation of Scrum and still baffles many. Old school Scrum was very apprehensive about Scrum being used beyond software development. No prize for guessing that the inventors and early followers were from a software development background, and they never thought of taking…
In a Scrum project, every sprint begins with Sprint Planning Meeting. The main objective should only be planning the sprint. Ensure that the meeting is attended by the all team members including the Product Owner, Scrum Master and the Scrum Team. You can also include part time resources for this meeting. This provides an important…
