2marks

1. What is Agile software development?

Agile software development is a set of methodologies based on iterative development,

where requirements and solutions evolve through collaboration between cross-functional
teams. Agile promotes continuous delivery, customer collaboration, and adaptability to
change.

2. When do daily stand-ups become valuable?

Daily stand-ups become valuable when teams use them to align on progress, identify
obstacles, and adjust their plan for the day. They help keep everyone focused, foster
communication, and improve accountability.

3. Agile is a Mindset – Justify

Agile is more than just a process or methodology; it’s a mindset focused on delivering value
to customers through continuous improvement, collaboration, and adaptability. It
emphasizes flexibility in the face of change, iterative learning, and responding to feedback,
rather than following rigid plans.

4. “No silver bullet process or practice makes projects run perfectly” – Why?

There’s no single process or practice that guarantees project success because every project
has its own unique challenges, requirements, and dynamics. Agile acknowledges that success
depends on the adaptability of the team, continuous learning, and responding to change,
rather than relying on one-size-fits-all solutions.

5. Differentiate between Agile and Waterfall approach:

Agile Waterfall

Iterative and incremental development Linear and sequential development

Flexibility to change requirements Requirements are fixed at the beginning

Continuous customer collaboration Customer involvement mainly at milestones

Frequent delivery of small increments Delivery happens at the end of the project

Testing is integrated throughout the process Testing happens after development

6. “The Agile Manifesto Helps Teams See the Purpose Behind Each Practice” – How?

The Agile Manifesto provides principles and values that guide teams in understanding the
purpose behind their practices. It emphasizes individuals and interactions over processes,
working software over documentation, customer collaboration over contracts, and
responding to change over following a plan. These principles help teams focus on value
delivery rather than just following procedures.

7. Advantages of Scrum Methodology:

 o Encourages collaboration and self-organization

o Promotes adaptive planning and quick feedback

o Allows for frequent delivery of valuable product increments

o Helps teams focus on high-priority tasks

o Increases transparency and accountability through regular stand-ups and reviews

8. What is a Daily Stand-Up?

A daily stand-up is a short, time-boxed meeting where team members discuss what they
worked on yesterday, what they will work on today, and any obstacles they’re facing. The
purpose is to synchronize the team and ensure progress is made towards the sprint goal.

9. What is a Task Board?

A task board is a visual representation of tasks in an Agile project. It typically includes

columns such as "To Do," "In Progress," and "Done," allowing the team to track the status of
each task and monitor workflow.

10. What is Time Boxing Iterations?

Time boxing iterations is the practice of setting a fixed period, known as a time box (e.g., 1-2
weeks), for completing a set of tasks or delivering a product increment. This helps teams
maintain focus, work at a sustainable pace, and continuously deliver value.

11. List the Benefits of Agile:

 Flexibility and adaptability to change

 Continuous delivery of valuable software

 Customer satisfaction through frequent feedback

 Enhanced team collaboration and communication

 Early detection of issues and risks

 Better alignment with business goals

12. What is the purpose of a Sprint Review?

The Sprint Review is a meeting held at the end of a sprint to inspect the work completed and
gather feedback from stakeholders. It ensures the product meets customer needs and allows
the team to adjust priorities for the next sprint based on feedback.

13. What does the principle of welcoming changing requirements entail?

This Agile principle encourages teams to embrace changes in requirements, even late in the
development process. It reflects Agile’s flexibility and focus on delivering value, allowing
teams to adapt and ensure that the product meets evolving customer needs.

14.What are the three pillars of Scrum?

 o Transparency: Ensures all team members and stakeholders have a clear
understanding of the work.

o Inspection: Regularly reviewing progress to detect issues.

o Adaptation: Adjusting processes or goals based on inspection results.

15.What are the 3 roles in Scrum?

o Product Owner: Defines the product vision and manages the backlog.

o Scrum Master: Facilitates Scrum processes and removes obstacles.

o Development Team: Builds and delivers the product increment.

16.Who attends the Sprint Review?

The development team, product owner, Scrum master, stakeholders, and other key individuals
interested in the product outcome.

17.Difference between Sprint Planning and Sprint Retrospective:

o Sprint Planning: Determines what work will be done during the sprint.

o Sprint Retrospective: Reflects on the last sprint to identify improvements.

18.What is Burndown Chart? A graphical representation showing the remaining work in a sprint or
project, helping teams track progress toward completion.

19.What is a Sprint? A time-boxed iteration (usually 1-4 weeks) where a specific set of
features is developed. Planning involves selecting backlog items, and execution focuses on
completing them within the time frame.

20.What are the roles in Scrum?

o Product Owner

o Scrum Master

o Development Team

21.What are the 5 Scrum values?

o Commitment

o Courage

o Focus

o Openness

o Respect

22.Describe Scrum Framework:

Scrum consists of roles (Product Owner, Scrum Master, Development Team), artifacts (Product
Backlog, Sprint Backlog, Increment), and events (Sprint Planning, Daily Stand-Up, Sprint Review,
Sprint Retrospective).
23.Describe Sprint Artifacts:

o Product Backlog: List of features and tasks for the product.

o Sprint Backlog: Selected items from the Product Backlog for the current sprint.

o Increment: The working product produced after a sprint.

24.Describe Sprint Ceremonies/Events:

o Sprint Planning

o Daily Stand-Up

o Sprint Review

o Sprint Retrospective

25.Define Sprint Review:

A meeting at the end of a sprint where the team presents the completed work to
stakeholders and receives feedback.

26.Define Zero Sprint:

An informal term for the preparatory phase before the first sprint, where setup and initial
groundwork are done (e.g., setting up tools, creating the backlog).