ATRIA INSTITUTE OF TECHNOLOGY

(An Autonomous Institution, Bengaluru)

Approved by AICTE, Affiliated to VTU,
Belagavi
Accredited by NAAC A++ & NBA
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

AGILE TECHNOLOGIES
Module-4
Planning: Vision, Release Planning, The Planning Game, Risk
Management, Iteration Planning, Slack, Stories, Estimating.
Developing: Incremental requirements, Customer Tests, Test-Driven
Development, Refactoring, Simple Design, Incremental Design and
Architecture, Spike Solutions, Performance Optimization,
Exploratory Testing.

1. Planning
 Planning in Agile is iterative and adaptive rather than rigid and
predictive.
 Instead of one big upfront plan, Agile projects are divided into
iterations or sprints (1–4 weeks).
 Teams hold planning sessions to:
o Prioritize backlog items.
o Estimate effort.
o Define short-term goals.
 Benefits:
o Continuous feedback.
o Rapid adaptation to change.
o Alignment with stakeholder needs.
o Delivery of incremental value at regular intervals.
 ATRIA INSTITUTE OF TECHNOLOGY
(An Autonomous Institution, Bengaluru)
Approved by AICTE, Affiliated to VTU,
Belagavi
Accredited by NAAC A++ & NBA
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

2. Vision
 Definition: A clear and concise statement that describes the
purpose, goals, and outcomes of the project.
 Purpose:
o Acts as a guiding star for the team.
o Keeps everyone aligned on common goals.
o Motivates the team with a clear purpose.
 Components:
o What the product will achieve.
o Who the target users are.
o Why it is valuable.

3. Release Planning
 A high-level plan that defines when and what features will be
released to customers.
 Involves:
o Defining a release vision.
o Prioritizing high-value features.
o Estimating effort and timeline.
o Aligning business goals with development capacity.
 Ensures:
o Stakeholder expectations are clear.
o Delivery happens iteratively and incrementally.
o Risks are minimized by delivering early and often.
 ATRIA INSTITUTE OF TECHNOLOGY
(An Autonomous Institution, Bengaluru)
Approved by AICTE, Affiliated to VTU,
Belagavi
Accredited by NAAC A++ & NBA
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

4. The Planning Game (XP Practice)

 A collaborative activity between developers and customers.
 Customers: Prioritize features based on business value.
 Developers: Estimate the effort required.
 Together they select features for the next iteration.
 Benefits:
o Balances business priorities and technical feasibility.
o Ensures the most valuable features are delivered first.
o Builds a shared understanding of goals.

5. Risk Management
 Continuous identification, analysis, and mitigation of risks.
 Integrated into daily Agile practices like:
o Stand-up meetings.
o Sprint planning.
o Retrospectives.
 Benefits:
o Proactive issue resolution.
o Reduces chances of project failure.
o Ensures timely delivery and budget control.
 ATRIA INSTITUTE OF TECHNOLOGY
(An Autonomous Institution, Bengaluru)
Approved by AICTE, Affiliated to VTU,
Belagavi
Accredited by NAAC A++ & NBA
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

6. Iteration Planning
 Focused on short-term execution (per sprint).
 Steps:
o Review product backlog.
o Select highest-priority items.
o Break them into tasks.
o Estimate effort and assign responsibility.
 Goal: Deliver a working increment at the end of the iteration.

7. Slack
 Intentional buffer time added into plans.
 Helps manage:
o Unexpected delays.
o Scope changes.
o Extra reviews and feedback.
 Benefits:
o Ensures quality.
o Reduces stress on the team.
o Makes the workflow smoother and more adaptable.

8. Stories (User Stories)

 Lightweight requirements representation.
 Format:
 ATRIA INSTITUTE OF TECHNOLOGY
(An Autonomous Institution, Bengaluru)
Approved by AICTE, Affiliated to VTU,
Belagavi
Accredited by NAAC A++ & NBA
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

"As a [user type], I want [feature] so that [benefit]."

 Captures who, what, and why clearly.
 Benefits:
o Promotes collaboration between business and technical
teams.
o Helps prioritize work.
o Ensures software delivers real value.

9. Estimating
 Agile teams estimate effort and complexity, not exact timelines.
 Techniques:
o Story Points (relative effort).
o T-shirt Sizing (S, M, L, XL).
 Purpose:
o Helps prioritize tasks.
o Promotes transparency.
o Embraces uncertainty while ensuring predictable delivery.

10. Developing
 Agile development is iterative and incremental.
 Practices:
o Test-Driven Development (TDD).
o Continuous Integration.
 ATRIA INSTITUTE OF TECHNOLOGY
(An Autonomous Institution, Bengaluru)
Approved by AICTE, Affiliated to VTU,
Belagavi
Accredited by NAAC A++ & NBA
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

o Refactoring.
 Developers work closely with customers.
 Goal: Deliver working software quickly while adapting to
change.

11. Incremental Requirements

 Requirements are not fixed upfront.
 Defined and refined incrementally as the project progresses.
 Benefits:
o Flexibility to adapt to change.
o Ensures product always aligns with customer needs.
o Reduces waste from unnecessary features.
12. Customer Tests
 Tests are written from the customer’s perspective.
 Validate that features meet business needs.
 Usually expressed as acceptance criteria for user stories.
 Promotes continuous feedback and ensures delivery of real
customer value.

13. Test-Driven Development (TDD)

 Process:
1. Write a failing test.
2. Write minimum code to pass test.
3. Refactor code for quality.
 ATRIA INSTITUTE OF TECHNOLOGY
(An Autonomous Institution, Bengaluru)
Approved by AICTE, Affiliated to VTU,
Belagavi
Accredited by NAAC A++ & NBA
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

 Benefits:
o Fewer bugs.
o Simpler, modular design.
o Maintains high test coverage.

14. Refactoring
 Improving internal structure of code without changing
behavior.
 Benefits:
o Cleaner, more maintainable code.
o Reduction of technical debt.
o Easier debugging and enhancements.

15. Simple Design

 Principle: “Do the simplest thing that works.”
 Avoid over-engineering or adding unnecessary features.
 Leads to clarity, maintainability, and adaptability.

16. Incremental Design

 Design evolves gradually as the system grows.
 Start with a basic architecture → refine as new requirements
emerge.
 Helps in adapting to changing customer needs.
 ATRIA INSTITUTE OF TECHNOLOGY
(An Autonomous Institution, Bengaluru)
Approved by AICTE, Affiliated to VTU,
Belagavi
Accredited by NAAC A++ & NBA
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

17. Incremental Design and Architecture

 Extends incremental design to include system-wide
architecture.
 Focus on delivering small increments while improving
underlying architecture.
 Benefits:
o Faster adaptation to change.
o Ability to integrate new technologies.

18. Spike Solutions

 Short, time-boxed research activity to investigate unknowns.
 Examples:
o Testing a new API.
o Exploring a new database.
 Helps in reducing technical risks and uncertainty.

19. Performance Optimization

 Continuous activity in Agile, not postponed until the end.
 Focus on:
o Eliminating bottlenecks.
o Optimizing databases, caching, and refactoring.
o Conducting load testing.
 Ensures smooth, efficient user experience.
 ATRIA INSTITUTE OF TECHNOLOGY
(An Autonomous Institution, Bengaluru)
Approved by AICTE, Affiliated to VTU,
Belagavi
Accredited by NAAC A++ & NBA
DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS

20. Exploratory Testing

 Unlike scripted testing, testers explore freely.
 Encourages creativity to discover unexpected issues.
 Complements automation by finding hidden bugs.
 Valuable in fast-paced Agile projects where flexibility is key.