Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 251 views

    Agile Methodology: Introduction, Contents

    Uploaded by

    AMRUTHA R
    The document discusses the key roles and principles of agile methodology. The main roles are the Product Owner, who works with stakeholders to define requirements and vision; the Development Team, who builds the product; and the Scrum Master, who facilitates the process and removes impediments. The values of agile are also covered, including valuing individuals and interactions, working software, customer collaboration, and responding to change. Finally, the 12 principles of agile are introduced at a high level, such as self-organizing teams, frequent delivery, technical excellence, simplicity, and focus on continuous improvement.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Agile Methodology: Introduction, Contents

    Uploaded by

    AMRUTHA R
    251 views17 pages
    The document discusses the key roles and principles of agile methodology. The main roles are the Product Owner, who works with stakeholders to define requirements and vision; the Development Team, who builds the product; and the Scrum Master, who facilitates the process and removes impediments. The values of agile are also covered, including valuing individuals and interactions, working software, customer collaboration, and responding to change. Finally, the 12 principles of agile are introduced at a high level, such as self-organizing teams, frequent delivery, technical excellence, simplicity, and focus on continuous improvement.

    Original Title

    Agile presentation

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the key roles and principles of agile methodology. The main roles are the Product Owner, who works with stakeholders to define requirements and vision; the Development Team, who builds the product; and the Scrum Master, who facilitates the process and removes impediments. The values of agile are also covered, including valuing individuals and interactions, working software, customer collaboration, and responding to change. Finally, the 12 principles of agile are introduced at a high level, such as self-organizing teams, frequent delivery, technical excellence, simplicity, and focus on continuous improvement.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    251 views17 pages

    Agile Methodology: Introduction, Contents

    Uploaded by

    AMRUTHA R
    The document discusses the key roles and principles of agile methodology. The main roles are the Product Owner, who works with stakeholders to define requirements and vision; the Development Team, who builds the product; and the Scrum Master, who facilitates the process and removes impediments. The values of agile are also covered, including valuing individuals and interactions, working software, customer collaboration, and responding to change. Finally, the 12 principles of agile are introduced at a high level, such as self-organizing teams, frequent delivery, technical excellence, simplicity, and focus on continuous improvement.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 17

    Introduction,Contents

    Agile methodology
    Roles Introduction
    There are 3 main roles in agile methodology which work hand in hand to deliver quality products to
    client.

    Role 1
    PRODUCT OWNER

    Product owner as the name suggests is the owner of the project.

    He works with stakeholders/clients to get the right requirements.

    He is responsible to get requirements that the client might not see or comprehend at that time.

    Helps the development team to understand vision and the requirements.

    Hence product owner can also be called a bridge between the clients and the development team.

    He's responsible for Creates vision so development team can visualise expected outcome.

    Creates a Roadmap that summarises the vision and direction for the product.
    Role 2
    Role 3
    The third role of Agile Methodologies is Scrum Master.So lets have a look on Who is Scrum Master.

    1) He is Servant Leader not a line manager.

    2)He is a facilitator of scrum events rather than a task master.

    3)An impedient remover but not a technicaloe design authority.

    4)Not a Decision maker but a process coach.

    Scrum Master plays a very important role in Agile.Here Some of the Responsibilities of Scrum
    Master:

    1)He monitor project progress,provides timely feedback& drives a culture of agility and learning.

    2)he also host regular sessions to share updates with Product stakeholders about how project
    progeessing or not.

    3)To improve effiecinecy ,Scrum master encouraged use of Continous Integration and
    automation.These Practises reduce development time,& improve the architecture & quality of the
    product.

    The scrum master forms an essentila link btwn Product ownee and Project team.So here are some of
    the top qualities of a succesful scrum master: 1) influential 2)collaborative 3)observant and 4 )
    Knowledgeable

    VALUES introduction
    Agile values provide a foundation to software developers which help them in making decisions about
    the best way to develop and ensure high-quality software is delivered to client.

    Let us now take a look at the 4 agile values individually and see how they must be implemented.
    Value 1
    Individuals interactions over procedures and tools, even though having high technical and processed
    tools, there is no cooperation among team members, effects the consistency, delays the project. For
    example a team member is quite inefficient and shows resentment towards work it effects on
    project work... So an effective collaboration between team members. So i believe individuals and
    interactions is necessary over tools and procedures

    Value 2

    2. Working Software over Comprehensive Documentation


    In traditional approach of software development, team spends months to
    gather and write all customer requirements at the beginning of the project.
    Eventually, these documents will out of date at the time, we are done with
    requirements.
    This doesn't mean we should not write documents.

    The Agile prefers working software with minimal documentation, Because


    • Working software is the measure of progress and is more useful and
    practical.
    • Agile saves more time to concentrate on development.
    • It provides oppurtunity for rapid feedback.
    • And makes product delivery fast.
    Value 3
    Value 4

    Principles Introduction
    Principle 1
    Principle 2

    Principle 3
    Principle 4
    Principle 5
    Collaboration between Stakeholders and development teams:

    -The representative of business stakeholders is only point of contact between development team
    and customer.

    -It leads to helps to early detection and resolution issues.

    -The more engaged of the stakeholders are right from the start,the more improved will be outcome
    of the project.

    Principle 6
    Principle 7
    Principle 8

    Principle 9
    Principle 10
    Organising team

    In traditional software development technologies we can see pyramid shaped teams where
    mangament makes a key fdecisions for contributors.

    But this principal suggest dat use of self organised team s which work with more flat management
    type where decisions are made on a group rather than by a singular manager of management team.

    Then How it looks in practise : self organised teams are autonomous group within the organisation
    who takes the control & responsibilities over their respective areas and have ownership of theose
    areas .

    In conclusive we can say this principal as" The Best Architecture requirements and designs emerge
    from selg organising teams"
    Principle 11
    Maintaining consistency is hard.. a team should possess quality of being committed consistent
    towards work, which helps improvement of works overtime

    Principle 12
    Conclusion

    You might also like