One of the guiding principles of Scrum is to develop the functionality of the highest priority to the customer first. Less important features are developed in subsequent Sprints or can be left out altogether according to the customer’s requirements. This approach gives the Scrum Team the required time to focus on the quality of essential…
Using the term “master” to describe someone’s boss today often conjures images of Igor addressing Dr. Frankenstein, Renfield heeding Count Dracula’s dark biddings or The Mountain doing Cersei’s dirty work. But in Scrum, the Master is one who serves you. As a Scrum project begins, one of the important activities or processes is to identify…
The term “agile” generally refers to being able to move or respond quickly and easily; being nimble. In any kind of management discipline, agile as a quality should therefore be a good thing to aim for. Agile project management specifically, involves being adaptive during the creation of a product, service, or other result. A number…
The Agile Manifesto stresses “customer collaboration over contract negotiation.” The Scrum framework adopts an approach in which the Scrum Core Team members collaborate with each other and the stakeholders to create the deliverables that provide the greatest possible value to the customer. According to A Guide to the Scrum Body of Knowledge (SBOK™), collaboration ensures that…
When something goes wrong with a project, who gets blamed? If you are the Product Owner, Scrum Master or Project Manager, you’re probably saying that the leader gets the blame. If you’re a Scrum Team or development team member, you’re probably saying, “We always get blamed.” What if the reality of the situation is it’s…
A Scrum project often goes through a number of phases. Five phases, composed of nineteen processes, are suggested in A Guide to the Scrum Body of Knowledge (SBOK™). The Release phase is the final stage of a Scrum project. This phase includes two processes that emphasize delivering the Accepted Deliverables to the customer and identifying,…
A Scrum project often goes through a number of phases. Five phases, composed of nineteen processes, are suggested in A Guide to the Scrum Body of Knowledge (SBOK™). After the Implement phase comes the Review and Retrospect phase. This phase includes three processes that focus on reviewing the deliverables and work that has been done…
A Scrum project often goes through a number of phases. Five phases, composed of nineteen processes, are suggested in A Guide to the Scrum Body of Knowledge (SBOK™). After the Plan and Estimate phase comes the Implement phase. This phase includes three processes related to the execution of tasks and activities—creating various deliverables, conducting Daily…
Scrum is not your regular waterfall technique but an agile framework which changes and, at times, challenges traditional roles. The Organizational Resource Matrix is a hierarchical depiction of a combination of a functional organizational structure and a projectized organizational structure. Matrix organizations bring together team members for a project from different functional departments such as…
A typical Prioritized Product Backlog will contain all User Stories, their time estimates (including any revised estimates), and the status of higher priority requirements. Any new or revised User Stories resulting from changes to business requirements, customer requests, external market conditions, and/or lessons learned from previous Sprints are also incorporated. Product Backlog Review Meeting Also…
