Agile Document
Agile Document
manage their work through a set of values, principles, and practices. Much like a ...
Ans :
Agile Waterfall
In Agile all the software development process is It is a linear sequencing model for developing
done in smaller parts, that called Sprint. and testing software.
Changes can be made at any time of Once the development started, requirement
development. cannot be changed.
It is a flexible method to build a software. It is a structure method for software
development.
Sprint Planning-Sprint planning is a collaborative meeting in Agile development where the product owner and the development team select
and commit to a set of user stories or tasks to be completed during an upcoming sprint.
a)
b) Sprint Review-thrusday -A Sprint Review is a Scrum event held at the end of a sprint where the development team
showcases the completed work to stakeholders and collects their feedback, facilitating transparency and collaboration.
c)
d) Daily Scrum Meeting-The Daily Scrum, also known as the Daily Standup, is a short, time-
boxed meeting in Agile methodologies where team members discuss their progress, plan for
the day, and identify any obstacles to keep the project on track.
e)
Ans : Product Backlog – A user requirement list for whole project according Priority, It is created by
Product Owner.
Sprint Backlog – Sprint Backlog is splitted part of Product Backlog. We break the Parts into
manageable Parts.
Que . What is Sprint ?
Ans : In Agile we do all the Process in smaller parts or small time duration, these time duration are
called SPRINT.
Ans : Product Owner keep all the accountability of all the requirements of Client that which
Requirement should be Processed First and which will go last.
Ans : User Story - It defines the Actual Business Requirement generally created by the Business
Owner.
Epic – A group of related User Stories is called an Epic or a bunch of User Stories is called an Epic.
Ans : It predict how much work Agile Team can complete in a Sprint and how much time will it
require to complete a Project .
Sure, here are simple one-line explanations with examples for SIT, UAT, and regression
testing:
1. **SIT (System Integration Testing):** Testing how different parts of a system work
together, like checking if the car's engine and transmission work smoothly together.
2. **UAT (User Acceptance Testing):** Testing by end-users to ensure the software meets
their needs, like customers testing a mobile app before its official release.
3. **Regression Testing:** Rechecking existing features to ensure they still work after
changes, like making sure a smartphone's older features (camera, calls) still function after a
software update.