There are three roles in scrum: Product Owner, Team, and Scrum Master. Together they are called The Scrum Team. The Product Owner is accountable for optimizing return on investment (ROI) by analysing product aspects, converting these into a priority-wise list so as to decide those things which should be at the top of the list for the…
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…
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…
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…
Coding and testing stages are not isolated ones but well integrated ones in Agile development. The development toward every user story commences through written business-interfacing experiments that enables the team the ‘what part’ regarding coding and also the juncture when the tasks are being completed with. Professionals in the field of testing, analysis and development…
Planning poker is combination of analogy, expert opinion, and disaggregation in a fun way so that it will result quick and reliable estimates. All the team members are included in planning poker. On any agile project, you will have typically ten team members or less. If it does, the team can be split in twos.…
