• Scrum Lesson 02 – Scrum Aspects

    by  • November 24, 2014 • Scrum and Agile • 0 Comments

    There are five scrum aspects which must all be addressed and managed throughout a scrum project.

    1. Organization
    2. Business Justification
    3. Quality
    4. Change
    5. Risk

    1. Organization

    Organization aspect of scrum framework defines roles and responsibilities under a scrum project which ensure the successful delivery of the projects. There are two categories of scrum roles:

    Core Roles

    These roles are fully committed with the project and are responsible for the success of the project. The core roles include Product Owner, Scrum Master, and Scrum Team.

    Non-Core Roles

    These roles are optional and informal roles. These roles may not be responsible for the successful delivery of the project. These roles include but not limited to stakeholders, vendors, chief product owner, chief scrum master.

    The details of the scrum roles including core and non-core roles will be given in the next lesson.

    2. Business Justification

    It is important to perform business assessment before starting a project due to the following reasons:

    • It helps the key decision makers understand the business need for a change, new product orĀ  a service.
    • It provides justification for moving forward with the project and its viability.
    • It is based on the concept of value-driven delivery.
    • Product owner is primarily responsible for business justification.
    • Other team members also contribute in the process.

    3. Quality

    In scrum, quality is defined as the ability to meet the acceptance criteria and achieve the business value expected by the customers.

    • To ensure quality, scrum adopts an approach of continuous improvement
    • The team learns from experience and stakeholder engagement to constantly keep the prioritized product backlog.
    • The prioritized backlog is never complete until the closure or termination of the project.
    • Changes to requirements reflect changes in the internal and external business environment.
    • Allows the team to continuously learn and adopt
    • Scrum requires work to be completed incrementally through sprints due to which errors are fixed right away
    • Quality related tasks including development, testing, and documentation are completed as part of a sprint.
    • Constant discussions between the scrum core team and stakeholders including the customers make sure the required quality is achieved
    • Ensures that the gap between customer expectations and actual deliverable is constantly reduced.

    4. Change

    Every project regardless of its methods or framework used is expected to change. It is imperative that project team members understand that the scrum development processes are designed to embrace change. The scrum team should try to maximize the benefits and minimize the negative impact that arise from change.

    Scrum Acknowledgements

    Stakeholders may change their mind about what they want during the course of the project which is known as “Requirements Churn“. It’s not feasible for stakeholders to define all requirements during project initiation. Scrum welcomes change by using iterative sprints. This enables customers to regularly interact with scrum team members, view deliverable, and change requirements.

    5. Risk

    Risk is defined as an uncertain event or set of events that can affect the objectives of a project and may contribute to its success or failure. Risk may be two types of impacts:

    • Positive impacts i.e. opportunities
    • Negative impacts i.e. threats

    Risk Management

    Managing risk must be done proactively. It is an iterative process that should begin at project initiation and continue throughout the project lifecycle. Risk management should follow standardized steps to ensure risks are:

    • Identified
    • Evaluated
    • Proper course of action is determined and acted upon

    Risks should be identified, assessed, and responded on the basis of two factors:

    • Probability of each risk occurring
    • Possible impact on the project

    Risk with high probability and impact value are determined by multiplying both factors and should be dealt with before those with the lower value. Once a risk is identified, it is important to manage the risk.




    Namecheap.com
    Avatar of admin

    About

    GetCodeSnippet.com provides you high quality Microsoft .NET development related articles, tutorials and sample code for ASP.NET, C#, VB.NET, AJAX, WCF, WPF, Web Services, Windows Services, SQL Server and other technologies.

    Leave a Reply