Task 4
Published: 2024-01-01 14:51:33

1. https://docs.google.com/spreadsheets/d/13ki-g9Di5_bpGVC5RaJHpw60yzDkORcoSqjUKUy9WJU/edit?usp=sharing

2.Agile Model : This is a SDLC (Software Development Life Cycle) model.
In this model, each module is divided into units. After completion of 1 unit it is released to the customers.
These units are called sprints.
Sprint: It is a continuous time-boxed life cycle.
No need to wait for the whole completion of module for client and customers.
After completion of one sprint then another sprint begins.
Eg : If there are 100 modules, then it is split into 10 sprints. each sprint will contain 10. After completion of 1 sprint, it is released to the customers.
Another sprint could begin after completion of previous sprint.
The duration of each sprint would be ranging from 2 weeks to 4 weeks depending upon the project.
Advantages : It can be used for larger projects.
No need to wait for the Client till the completion of whole module.
Client Interaction is possible if there are frequent changes in Requirement or Design Phase.
We can use this model if requirements are not stable.
This model is also called Iterative and Incremental Model.
Iterative Development: Software is developed and delivered to the customer, based on the feedback again the development cycle will happen.
Incremental Development: Software is developed in parts or increments. In each increment, a portion of requirement is delivered.
To implement this agile methodology we have many frameworks.
Framework: It is a set of rules to implement agile model.
They are: 
a)Scrum   
b)kanban  
c)Extreme Programming(XP)
Scrum framework is mostly used out of these all frameworks.
Scrum: It is a framework used to implement agile methodology.
Agile core values:
Individuals and interactions over processes and tools: This means individuals will interact about overall process to complete the project with the help of software tools as well.
Working software over comprehensive documentation: Rather following document, depending mostly on working software to complete the process.
Customer collaboration over contract negotiation: Here collaborating with customers rather than negotiating with them.
Responding to change over following a plan: Whenever client demands for changes in phases, then by following the plan, responding to changes.
In agile requirements are called User Stories.
Eg: Username, Password etc
These are the fields required for Login functionality.
These fields are called User Stories.
Collection of User Stories is called an Epic.
Eg: the entire Login functionality
Scrum roles: 
(i) Scrum Team: It is a self-organized team(There is no bossy culture)
It is a cross-functional team. All the members which includes business people, Developers, Testers work together.
Team size would be 6 or more depending upon the project.
(ii) Product Owner: He collects user stories from client.
He acts as a bridge between team and Client.
he will have technical knowledge and prioritize the user stories accordingly.
After completion of each sprint, he is the one who reviews and gives approval to release the sprint.
Product Backlog: In this, the user stories which are not yet assigned for any sprint are listed.
(iii) Scrum Master: He is protector of the team.
If the team is facing any issue, they should report it to Scrum master to get them resolved.
He is a person with knowledge in all the domains.
In scrum, we will have task board.
Task board: It shows the progress of the project.
It contains all user stories, To do list, In progress, To verify, Done tasks.
There can be physical task board or a software tool i.e., XIRA to list all these tasks.
Zero Sprint: It is a pre-preparation step to the first sprint. Activities like setting development environment, preparing backlog, etc need to be done before starting the first 
sprint and can be treated as Sprint zero.
Scrum Meetings:
i)Story grooming meeting: It is an open discussion between Scrum team and Product Owner.
Here story points are assigned i.e., how many hours and days are required to complete the work.
Story points are given with the help of planning poker tool.
Eg: 1 story point  = 4hrs 
ex: overall Login functionality = 12 hrs
ii) Sprint planning meeting: In this, PO, Scrum team, Senior managers will plan for sprint.
what are all the user stories they have to complete for the particular sprint, sprint duration, roles and responsibilities for each team member.
The time duration will be 2hrs * no. of weeks of sprint
iii) Daily Scrum meeting: This will happen everyday for 15 minutes.
In this they will give the updates of the sprint, and they will discuss what they did yesterday, what they gonna do for today and
What are all the blocks/difficulties they faced.
Scrum master will note down all the blocks.
Once the meeting gets end they will discuss this.
iv) Sprint review meeting: Before releasing the sprint to the client, the Product Owner will review the sprint, 
A demo will be conducted for sprint review to product owner.
The time duration will be 1hr * no. of weeks of sprint.
Here PO decides whether the sprint should gets released or not.
v) Sprint retrospective meeting: After sprint is released, what lessons the team has learnt from the sprint are discussed.
They use it for the upcoming releases.
The time duration will be 1hr * no. of weeks of sprint.
Sprint backlog: In this, modules which are assigned to sprint but not yet started are listed.
Spill over: If any user story which is not yet completed in the particular sprint is listed here.
We can able to move on to the next upcoming sprint.
This is all about Agile Methodology.

3. User Stories: In agile, requirements are called user stories.
Eg: For Login functionality, User name, Password and Login button are required for successful Login of an application.
These fields are called as user stories.
Epic: Collection of User stories is called an epic.
Eg: the entire Login functionality. It requires UN, Password and Login Button.