Unit 2
🎯 Unit 2 Overview
Unit 2 explains how Agile projects are planned, managed and delivered. It covers Agile teams,
Scrum teams, XP teams, team distribution, Agile project lifecycle, product vision, release planning,
product backlog, user stories, estimation, risk management and retrospectives.
Exam Tip: Agile project lifecycle, Scrum teams, product backlog, user stories, release planning and retrospectives are very important for RGPV exams.
👥 Planning for Agile Teams
Agile team planning means creating a team structure that supports collaboration, fast delivery
and continuous improvement.
Features of Agile Teams
- Self-organizing team
- Cross-functional members
- Frequent communication
- Shared responsibility
- Continuous feedback
- Customer-focused delivery
🏃 Scrum Teams
A Scrum team is a small Agile team responsible for delivering working software in short iterations
called sprints.
Scrum Team Roles
Product Owner
Defines product vision, manages backlog and prioritizes work.
Scrum Master
Guides the team, removes obstacles and ensures Scrum practices.
Development Team
Designs, develops, tests and delivers working software increment.
⚡ XP Teams
XP team follows Extreme Programming practices to improve code quality and customer satisfaction.
XP Team Practices
- Pair programming
- Test driven development
- Continuous integration
- Small releases
- Collective code ownership
- Refactoring
- Simple design
🌐 General Agile Teams
General Agile teams work with Agile values and principles. These teams may use Scrum, XP, Kanban
or a hybrid approach depending on project needs.
Important Qualities
- Collaboration
- Transparency
- Adaptability
- Accountability
- Continuous learning
- Focus on working software
📍 Team Distribution
Team distribution means Agile team members may work from the same location or different locations.
| Team Type |
Description |
| Co-located Team |
All members work from the same place. |
| Distributed Team |
Members work from different locations. |
| Hybrid Team |
Some members work together and others work remotely. |
Challenges in Distributed Teams
- Communication gap
- Time zone issues
- Coordination difficulty
- Less face-to-face interaction
- Tool dependency
🔄 Agile Project Lifecycle
Agile project lifecycle describes the stages through which an Agile project moves from idea to delivery.
Typical Agile Project Lifecycle
- Product vision
- Product roadmap
- Release planning
- Sprint planning
- Sprint execution
- Sprint review
- Sprint retrospective
- Product increment delivery
Agile lifecycle iterative hota hai, yani planning, development, testing aur feedback repeat hote rehte hain.
🧩 Phase Activities in Agile Project
| Phase |
Main Activities |
| Initiation |
Define vision, goals and stakeholders. |
| Planning |
Create backlog, estimate work and plan releases. |
| Execution |
Develop, test and integrate software. |
| Review |
Demonstrate working software and collect feedback. |
| Retrospective |
Discuss improvements for next iteration. |
| Release |
Deliver usable software to users. |
🎯 Product Vision
Product vision is a clear statement that explains what product will be built, who will use it
and what value it will provide.
Importance
- Gives direction to the team
- Helps in prioritization
- Aligns stakeholders
- Supports release planning
- Defines product purpose
📦 Product Backlog
Product backlog is a prioritized list of features, requirements, enhancements and fixes required
in the product.
Characteristics
- Managed by Product Owner
- Contains user stories and tasks
- Continuously updated
- Prioritized according to business value
- Acts as main source of work for team
📝 User Stories
User stories are short descriptions of features from the user's point of view.
User Story Format
As a [user], I want [feature], so that [benefit].
Example
As a student, I want to download notes, so that I can prepare for exams easily.
Good User Story Qualities
- Simple
- Clear
- Testable
- Valuable to user
- Small enough for sprint
⭐ Prioritizing and Estimating
Prioritizing means arranging backlog items according to importance. Estimating means predicting
effort required to complete work.
Prioritization Factors
- Business value
- Customer need
- Risk
- Dependency
- Cost and effort
Estimation Techniques
- Story points
- Planning poker
- T-shirt sizing
- Expert judgment
🚀 Release Planning
Release planning decides what features will be delivered in a product release and when they will be delivered.
Steps
- Define release goal.
- Review product backlog.
- Select high priority user stories.
- Estimate effort and velocity.
- Plan sprints for release.
- Finalize release schedule.
⚠️ Managing Risks and Issues
Agile manages risks continuously through short iterations, frequent feedback and regular inspection.
Common Risks
- Changing requirements
- Technical complexity
- Team unavailability
- Wrong estimation
- Poor communication
- Dependency delays
Risk Management Methods
- Daily stand-up meetings
- Sprint review
- Backlog refinement
- Early testing
- Continuous feedback
🔁 Retrospectives
Retrospective is an Agile meeting held at the end of iteration to discuss what went well,
what went wrong and what can be improved.
Retrospective Questions
- What went well?
- What did not go well?
- What should we improve?
- What actions should we take next?
Retrospective ka main goal team improvement hota hai.
⚖️ Scrum Team vs XP Team
| Scrum Team |
XP Team |
| Focuses on project management framework. |
Focuses on engineering practices. |
| Uses Scrum roles and events. |
Uses pair programming, TDD and refactoring. |
| Work happens in sprints. |
Work happens in short development cycles. |
| Best for managing Agile projects. |
Best for improving code quality. |
⭐ Important Questions
- Explain planning for Agile teams.
- Explain Scrum team roles.
- Explain XP teams and XP practices.
- Explain team distribution in Agile projects.
- Explain typical Agile project lifecycle.
- Explain phase activities in Agile project lifecycle.
- Define product vision and product backlog.
- What are user stories? Explain with example.
- Explain prioritizing and estimating in Agile.
- Explain release planning, risk management and retrospectives.
📌 PYQ Analysis
| Topic |
Exam Importance |
| Agile Project Lifecycle |
Very High |
| Scrum Teams |
High |
| Product Backlog |
Very High |
| User Stories |
Very High |
| Release Planning |
High |
| Risk Management |
Medium |
| Retrospectives |
High |
🔥 Last Minute Revision
- Agile teams are self-organizing and cross-functional.
- Scrum roles: Product Owner, Scrum Master, Development Team.
- XP teams focus on engineering practices.
- Product vision gives direction to the project.
- Product backlog is prioritized work list.
- User story format: As a user, I want feature, so that benefit.
- Release planning decides what and when to deliver.
- Retrospective is used for team improvement.