0% found this document useful (0 votes)
12 views14 pages

Agile

Uploaded by

22eg107a11
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views14 pages

Agile

Uploaded by

22eg107a11
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

AGILE:SCRUM,EXTREME

PROGRAMMING

ROLES AND RESPONSIBILITIES


D. VISHNU TEJA
P. ABHIRAMA RAO
P. RISHI TEJA
V. ANAND VARDHAN
P. MANIKANTA RISHI
AGILE MODEL AND TYPES OF AGILE FRAMEWORKS

Agile refers to the methods and best practices for organizing


projects based on the values and principles documented in
the Agile Manifesto. However, there’s no one right way to
implement Agile, and many different types of frameworks from
which to choose.
TYPES OF AGILE FRAMEWORK
▪ SCRUM
▪ EXTREME
▪ FEATURE DRIVEN DEVELOPMENT(FDD)
▪ DYNAMIC SYSTEMS DEVELOPMENT METHOD(DSDM)
SCRUM MODEL
Scrum is an Agile framework for managing and organizing work emphasizes
collaboration, flexibility, and customer satisfaction.

Roles:
•Product Owner: Represents the customer and is responsible for defining the
features and priorities of the product backlog.

•Scrum Master: Facilitates the Scrum process, ensures that the team adheres to
Scrum practices, and helps remove any impediments that may arise.

•Development Team: Cross-functional, self-organizing team responsible for


delivering increments of a product during each sprint.
FEATURES OF SCRUM
• Sprint: A time-boxed period (usually 2-4 weeks) during which a
potentially shippable product increment is created.
• Sprint Planning: A meeting at the beginning of each sprint where the
team plans the work to be done.
• Daily Scrum: A short daily meeting where team members discuss
progress, plan for the day, and identify any obstacles.
• Sprint Review: A meeting at the end of each sprint where the team
demonstrates the completed work to stakeholders.
• Sprint Retrospective: A meeting at the end of each sprint where the
team reflects on the sprint and identifies opportunities for improvement.
Advantages and disadvantages
▪ Advantages of Scrum:
1. Flexibility: Scrum allows for flexibility and adaptability in responding to changing
requirements.
2. Customer Satisfaction: Regular feedback and involvement of stakeholders lead to a
product that better meets customer needs.
3. Improved Communication: Daily stand-ups and regular meetings enhance
communication within the team.
4. Faster Delivery: Iterative development and short sprints contribute to a quicker product
delivery.
5. Risk Mitigation: Regular reviews and retrospectives help identify and address issues
promptly, reducing project risks.
Advantages and disadvantages

▪ Disadvantages of Scrum:
1. Uncertainty: The flexibility of Scrum may lead to uncertainty,
especially in projects with evolving requirements.
2. Time-Consuming: The meetings and ceremonies in Scrum can be
time-consuming, potentially impacting productivity.
3. Not Suitable for All Projects: Scrum may not be suitable for all
projects, especially those with highly regulated processes.
4. Dependency on Team Collaboration: Success heavily relies on
effective collaboration within the team.
Extreme Programming
▪ Extreme Programming is an Agile software development framework that aims
to improve software quality and responsiveness to changing customer
requirements.
Features of Extreme Programming (XP):
1. Pair Programming: Two programmers work together at one workstation,
switching roles frequently.
2. Test-Driven Development (TDD): Tests are written before the code, ensuring
that the code meets the specified requirements.
3. Continuous Integration: Code is integrated frequently, often multiple times a
day, to detect and address integration issues early.
4. Collective Code Ownership: The entire team is responsible for the codebase,
promoting collaboration and shared knowledge.
ADVANTAGES AND DISADVANTAGES
ADVANTAGES DISADVANTAGES
▪ Customer Satisfaction ▪ Risk of Scope Creep
▪ Flexibility and Adaptability ▪ Uncertain Planning
▪ High Code Quality and ▪ Customer Dependency
Collaboration
▪ Limited Applicability
▪ Rapid Delivery of Features
▪ Documentation Emphasis
▪ Continuous Improvement and
Feedback
ROLES AND RESPONSIBILITIES
BUSINESS OWNER
1. Strategic Decision-Making: Business owners play a crucial role in making important
decisions about the overall direction and objectives of the company.
2. Financial Management: They are responsible for overseeing the financial aspects of the
business, including budgeting, financial planning, and ensuring the company remains
financially healthy.
3. Leadership and Vision: Owners provide leadership to the team, setting a clear vision
and guiding the company toward its goals.
4. Risk Management: Identifying and managing risks is part of the owner's
responsibilities, making decisions that minimize potential challenges to the business.
5. Stakeholder Relationships: Building and maintaining positive relationships with
customers, employees, investors, and other stakeholders are vital for the success and
growth of the business.
PRODUCT MANAGER
1. Product Vision: Product managers define and communicate the overarching
vision and goals for a product.
2. Prioritization of Features: They decide which features are most important,
aligning development efforts with business objectives.
3. Cross-Functional Collaboration: Product managers work closely with
development, marketing, and other teams to ensure a coordinated and successful
product launch.
4. Market Analysis: Responsible for understanding market trends and customer
needs to guide product development and strategic decisions
DESIGNER

1. Visual Elements: They focus on the visual aspects, creating


aesthetically pleasing and functional designs for the product.
2. Collaboration with Teams: Designers work closely with
development and marketing teams to integrate design seamlessly into
the overall product strategy.
3. Creative Vision: Designers craft a creative vision for the product,
ensuring it aligns with brand identity and user expectations.
4. User Experience (UX): Ensuring a positive and intuitive user
experience is a primary responsibility of designers, enhancing overall
product usability.
BACKEND
1. Data Management: Backend developers handle data, storing and retrieving
information from databases.
2. Server Logic: They write code that runs on the server, processing requests
from the front end and sending back the right information.
3. Security: Backend developers focus on keeping data and processes secure,
protecting against unauthorized access and other potential threats.
4. Integration: They ensure different parts of the system (like databases and
servers) work together smoothly, enabling the entire application to function
properly.
FRONTEND

1. Look and Feel: Frontend developers make sure the website or app looks
good and is easy to use.
2. User Interface (UI): They design the buttons, menus, and other elements
users interact with on the screen.
3. Responsiveness: Frontend developers ensure the website or app works
well on different devices like phones, tablets, and computers.
4. Collaboration with Designers: They work closely with designers to turn
creative visions into actual, functional web pages or app screens.
5. Client-Side Logic: Frontend developers write code that runs on the user's
device, handling tasks like form validation and dynamic content display.
QUALITY ASSURANCE
1. Bug Catcher: Quality assurance (QA) folks find and fix mistakes or
"bugs" in the software to make it work better.
2. Testing Expert: They try out the software like a user would to make
sure it does what it's supposed to do.
3. Quality Checker: QA ensures the software is good quality, meaning
it's reliable and doesn't break easily.
4. Process Improver: They suggest ways to make the development
process better so the team can create even better software

You might also like