UNIT-1: SECTION – A

1. Define Extreme Programming (XP):

XP is an Agile so ware development methodology that focuses on improving
so ware quality and responsiveness to changing requirements. It encourages
frequent releases, pair programming, simple design, con nuous tes ng, and
customer collabora on. XP ensures that teams deliver working so ware quickly
and efficiently.

2. Discuss the concept of agility in so ware development:

Agility is the ability of a team to rapidly adapt to changes in requirements and
technology. It promotes itera ve development, con nuous feedback, and ac ve
customer involvement. Agility helps in minimizing risks and delivering value
incrementally.

3. What is the main goal of Extreme Programming (XP)?

The main goal of XP is to develop high-quality so ware quickly and adapt to
changing customer requirements. It emphasizes frequent releases, customer
feedback, and team collabora on to achieve this goal. XP ensures be er
sa sfac on and lower defect rates.

4. Name one key principle of Agile development:

One key principle is "Customer collabora on over contract nego a on." Agile
promotes close interac on with customers to ensure that their needs are
con nuously met. This helps in delivering relevant and valuable so ware.

5. What is the importance of organiza onal success in Agile methodologies?

Agile methodologies contribute to organiza onal success by improving product
quality, speeding up delivery, and enhancing team performance. They encourage
adaptability, innova on, and customer sa sfac on, which are crucial for business
growth.

6. What are some key prac ces involved in prac cing XP?
XP includes prac ces like pair programming, test-driven development, con nuous
integra on, collec ve code ownership, simple design, and frequent releases.
These prac ces help in maintaining quality and improving team coordina on.

7. Name one technique used in XP for problem-solving during development:

Root Cause Analysis (RCA) is used to iden fy underlying problems in the
development process. It helps prevent recurring issues and promotes con nuous
improvement. RCA ensures that teams address the real source of problems.
8. What is the recommended approach regarding crea ng Agile methods?
Agile methods should be customized based on the project’s needs and team
dynamics. Teams should start with a framework and adapt it over me through
feedback and retrospec ves. This approach allows flexibility and con nuous
improvement.

9. Discuss Prac cing XP and Root cause analysis for extreme programming:
Prac cing XP involves following its principles like simplicity, feedback, and
courage. Root cause analysis is used in XP to find and fix the underlying cause of
bugs or inefficiencies. This leads to be er so ware quality and team learning.

10. State and explain the need for Agile methodology process model:
Agile methodology is needed to address rapid changes in customer needs and
technology. It enables incremental delivery, encourages feedback, and improves
collabora on. Agile ensures that so ware remains relevant and valuable
throughout its development.

UNIT-2: SECTION – A

1. How to hold a daily standup mee ng?

A daily standup is a short (15-minute) mee ng held each day with the team
standing. Each member answers three ques ons: What did I do yesterday? What
will I do today? Are there any impediments? It promotes communica on and
quick issue resolu on.

2. What role does a real customer play in Agile development?

A real customer ac vely par cipates by providing feedback, priori zing features,
and clarifying requirements. Their involvement ensures the product meets actual
business needs and evolves according to market demands.

3. What is the significance of trust in Agile collabora on?

Trust fosters open communica on, mutual respect, and be er teamwork. It
enables teams to work transparently, take risks, and innovate. In Agile, trust is key
to building a collabora ve and empowered work environment.

4. Explain coding standards and collec ve ownership in so ware process

development:
Coding standards ensure consistent and readable code across the team. Collec ve
ownership means all team members can modify any part of the codebase. These
prac ces increase flexibility, reduce bo lenecks, and improve code quality.
5. Define "ubiquitous language" in the context of Agile collabora on:
Ubiquitous language is a common vocabulary shared by developers, testers, and
stakeholders. It ensures clear communica on and understanding of business
terms and processes. It reduces confusion and aligns everyone’s understanding.

6. How to deal with disagreement regarding coding standards in the team?

Disagreements should be resolved through open discussions and team consensus.
A documented standard can be created and reviewed regularly. It’s important to
priori ze team harmony and maintain quality.

7. Why are coding standards important in Agile teams?

They ensure consistency, reduce errors, and make code easier to maintain.
Standards help new team members understand the code quickly. They support
collec ve ownership and speed up development.

8. What are the typical types of mee ngs in Agile development?

Agile mee ngs include daily standups, sprint planning, sprint reviews, sprint
retrospec ves, and backlog grooming sessions. Each mee ng serves a specific
purpose in planning, feedback, and improvement.

9. List the members involved in Extreme Programming and write each member's
role:

o Customer: Provides requirements and feedback.

o Developer: Writes and tests code.

o Coach: Ensures proper XP prac ces.

o Tracker: Monitors progress.

o Tester: Writes and runs automated tests.

10. What is an itera on demo? How does it help the team?

An itera on demo showcases the work completed in a sprint to stakeholders. It
helps gather feedback and verify if the product meets expecta ons. It ensures
transparency and alignment with customer goals.
UNIT-3: SECTION – A

1. What is the goal of a bug-free release in Agile development?

The goal is to deliver reliable, high-quality so ware that meets user expecta ons
without errors. Frequent tes ng and con nuous integra on help minimize bugs. A
bug-free release increases customer trust and sa sfac on.

2. Why is fast build important in Agile development?

Fast builds ensure quick feedback, allowing developers to iden fy and fix issues
early. It supports frequent integra on and smooth delivery. Speed in builds
improves produc vity and reduces delays.

3. Demonstrate collec ve code ownership:

In collec ve ownership, every team member can change any part of the codebase.
This encourages collabora on, faster bug fixing, and con nuous improvement. It
avoids silos and increases team responsibility.

4. Define con nuous integra on in Agile prac ces:

Con nuous integra on involves regularly merging code into a shared repository,
followed by automated tes ng. It helps detect issues early and keeps the system
in a deployable state at all mes.

5. Why is documenta on important in Agile releasing?

Documenta on provides essen al informa on for maintenance and future
development. Agile promotes lightweight, useful documenta on rather than
exhaus ve records. It ensures clarity without slowing down progress.

6. What does collec ve ownership mean in the context of releasing?

It means all team members are responsible for the quality and success of the
release. Everyone contributes to ensuring that features work well and meet user
expecta ons.

7. How does Agile releasing differ from tradi onal so ware releasing?
Agile releasing is incremental, frequent, and customer-focused. Tradi onal
releasing is planned long in advance and delivered in large batches. Agile allows
faster delivery of value and quicker feedback.

8. What role does tes ng play in Agile releasing?

Tes ng ensures that each release is func onal, stable, and meets requirements.
Automated and manual tests are used throughout the cycle. It helps in iden fying
bugs early and maintaining quality.
9. How does Agile releasing support customer sa sfac on?
Frequent releases mean customers get new features quickly and can give feedback
early. This responsiveness builds trust and ensures the product aligns with
customer needs.

10. What are some key factors to consider for a successful release in Agile?
Key factors include code quality, customer readiness, automa on, team
coordina on, and proper planning. Tes ng and deployment prac ces also play a
vital role in ensuring success.

UNIT-4: SECTION – A (Improved Answers)

1. What is the purpose of version planning in Agile development?

Version planning helps teams outline what features or user stories will be delivered
in each version of the product. It allows the team and stakeholders to have a clear
vision of product progress. This planning aligns development goals with business
needs. It also helps in se ng realis c deadlines. The team adjusts the version plan
as requirements change.

2. Define a release plan in Agile methodology:

A release plan describes how and when a so ware product will be delivered to the
customer. It includes the meline, features, and itera ons for the release. The plan
is created based on customer priori es, team velocity, and business goals. It is
flexible and changes with feedback. The plan helps in delivering usable so ware
frequently.

3. What is the role of risk management in Agile planning?

Risk management iden fies and addresses poten al problems that may affect the
project. In Agile, risks are handled early using short itera ons and constant
feedback. High-risk features are tackled in early sprints. This reduces the impact of
surprises later. Agile’s flexibility also allows teams to adapt to unexpected changes
quickly.

4. Explain the concept of itera on planning in Agile development:

Itera on planning is done before the start of each itera on (sprint). The team
selects user stories from the product backlog and breaks them into tasks. They
es mate effort and assign work. This helps the team stay focused and organized
during the sprint. It also ensures everyone knows their role and goal.

5. What does "slack" refer to in Agile planning?

Slack refers to a small amount of buffer me added to the schedule. It is not
assigned to any task but is kept aside for unexpected work or delays. Slack
improves project flexibility and helps teams handle urgent changes or problems. It
reduces stress and keeps the project on track.

6. What are user stories in the context of Agile planning?

User stories are short, simple descrip ons of features told from the user's
perspec ve. They follow the format: "As a [user], I want [feature] so that
[benefit]." Stories help the team understand the purpose of the feature. They guide
development, tes ng, and priori za on. Each story should have acceptance
criteria.

7. Why is es ma ng important in Agile planning?

Es ma on helps the team predict how much work can be done in an itera on. It
helps in planning tasks, managing me, and se ng realis c goals. Es ma ons are
done using story points or hours. Good es mates help reduce risk and improve
delivery accuracy. It also helps in tracking team performance.

8. How does Agile planning differ from tradi onal project planning methods?
Agile planning is flexible, adap ve, and done in small cycles. Tradi onal planning is
fixed and done mostly at the beginning. Agile allows frequent changes and
feedback. Tradi onal methods are more rigid and difficult to change. Agile focuses
more on delivering working so ware con nuously.

9. What role does priori za on play in Agile planning?

Priori za on ensures that the most valuable features are developed first.
Customers and product owners decide which tasks bring the most value. This helps
in be er me and resource management. It ensures the team delivers important
features early. Priori za on also supports faster feedback and sa sfac on.

10. How does Agile planning facilitate adaptability and flexibility in project
execu on?
Agile planning uses short sprints, feedback loops, and user stories. This helps teams
adjust plans based on new informa on or changing needs. Frequent reviews and
retrospec ves improve the plan con nuously. Agile welcomes change, making the
project more adaptable. It helps deliver be er products over me.
UNIT-5: SECTION – A

1. What are incremental requirements in Agile development?

Incremental requirements are added in parts as the project moves forward. They
evolve based on customer feedback and learning during development. Agile does
not collect all requirements upfront. Instead, it focuses on delivering small, usable
features step by step. This improves flexibility and customer sa sfac on.

2. Define customer tests in the context of Agile development:

Customer tests are acceptance tests wri en to check if a feature meets the user's
expecta ons. They are created before development starts and act as criteria for
success. These tests guide the team and confirm that the product works as
expected. Passing customer tests means the feature is ready for release.

3. What is test-driven development (TDD)?

TDD is a prac ce where tests are wri en before the code. First, a test case is
created, which ini ally fails. Then, code is wri en to pass the test, and finally, the
code is improved through refactoring. This approach ensures be er design and
fewer bugs. It also builds confidence in the codebase.

4. Explain the concept of refactoring in Agile so ware development:

Refactoring is the process of changing the internal structure of code without
changing its func onality. It improves code readability, simplicity, and
maintainability. In Agile, refactoring is done regularly to keep the code clean. This
helps in adap ng to new changes quickly and reduces technical debt.

5. What does incremental design and architecture mean in Agile development?

Incremental design means designing the system gradually as development
progresses. Instead of building the en re architecture upfront, only what's needed
now is designed. This helps reduce waste and allows flexibility. The design evolves
through itera ons, adap ng to changing requirements.

6. Describe the purpose of spike solu ons in Agile development:

A spike is a short research or explora on task used to reduce uncertainty. Spikes
help the team understand complex problems, es mate effort, or test technical
solu ons. They are me-boxed and used when the team needs more knowledge
before star ng development. Spikes improve decision-making.

7. Why is performance op miza on important in Agile development?

Performance op miza on ensures the applica on runs efficiently, even as new
features are added. In Agile, performance is monitored con nuously, not just at the
end. Poor performance can impact user experience. Op miza on helps in building
scalable and responsive systems that meet customer needs.

8. What is exploratory tes ng in Agile methodology?

Exploratory tes ng is an informal tes ng approach where testers explore the
applica on without predefined test cases. They use their crea vity and intui on to
find bugs. It is especially useful when tes ng new features. Exploratory tes ng
helps discover unexpected issues and improves quality.

9. How does Agile development support itera ve development?

Agile breaks the project into small itera ons (sprints), where each delivers working
so ware. A er every itera on, feedback is gathered and improvements are made.
This cycle repeats un l the final product is ready. Itera ve development ensures
be er quality and customer alignment.

10. What role do user stories play in Agile development?

User stories help capture requirements in simple language. They focus on what the
user needs and why. Stories guide the team during development, tes ng, and
planning. They help in priori zing features and understanding customer
expecta ons. Well-wri en user stories lead to be er product outcomes.