Agile Methodology

Jira and Agile Methodology

1)What is agile? it is an incremental methodology basically used in Project management

2)Agile Principal: What are Agile Principles? The 12 Agile principles • Customer Satisfaction • Welcome Change • Deliver Frequently • Work Together • Motivated Team • Face-to-face • Working Software • Constant Pace • Good Design • Simplicity • Self-Organization • Reflect and Adjust

3)Agile methods/frameworks are Scrum, Kanban, Extreme Programming, and DSDM stands for Dynamic Systems Development Method

4)Agile Artifacts: What are the Scrum Outputs/artifacts?

1. Product Backlog: The Product Backlog is a prioritized list of user stories, features, and requirements that need to be implemented in the product. It is managed and maintained by the Product Owner.

2. Sprint Backlog: The Sprint Backlog is a subset of the Product Backlog and contains the list of tasks and user stories that the Development Team commits to complete within a Sprint.

3. Increment: The Increment is the sum of all the completed and potentially shippable product backlog items at the end of a Sprint. It represents a usable and potentially releasable version of the product.

4. Sprint Goal: The Sprint Goal is a short statement that describes the objective or purpose of the Sprint. It provides a clear focus and direction for the Development Team during the Sprint.

5. Agile Ceremonies:

What is Sprint? Sprint is a process of s a time-boxed iteration during which the Scrum Team works to complete a set of prioritized sprint backlog items.(2 to 4 weeks)

How many scrum meetings/ events occurred?

1. Sprint Planning: This meeting marks the beginning of the sprint and involves the Product Owner and Development Team. They collaborate to determine which backlog items will be worked on during the sprint and create a sprint goal.

2. Daily Scrum: Also known as the daily stand-up, this is a short daily meeting for the Development Team to synchronize their activities. Each team member answers three questions: What did I do yesterday? What will I do today? Are there any obstacles in my way?

3. Sprint Review: At the end of the sprint, the Development Team presents the completed work to the stakeholders and gathers feedback. The Product Owner assesses the work completed against the sprint goal.

4. Sprint Retrospective: This meeting occurs after the Sprint Review and is an opportunity for the Scrum Team to reflect on the sprint and identify areas for improvement. They discuss what went well, what could be improved, and define action items for the next sprint.

6)Agile Reports/Scrum chart:

How many scrum charts?

1. Burndown Chart: Tracks remaining work over time in a sprint or project, helping the team monitor progress and stay on track.

2. Velocity Chart: Shows average work completed by the team in each sprint, aiding in future work estimation and project timeline planning.

3. Cumulative Flow Diagram: Visualizes work flow through different stages, identifies bottlenecks, and evaluates overall workflow efficiency.

4. Release Burndown Chart: Tracks progress of completing backlog items or features over time, ensuring alignment with planned scope and release date.

5. Sprint Goal Chart: Illustrates the sprint goal and key objectives, keeping the team focused and aligned throughout the iteration.

6. Team Task Board: Visualizes tasks or user stories within a sprint, promoting transparency and collaboration among team members.

7)What is a user story?

It is nothing but a requirement or feature given by a business user to build the application or product, and how to build the feature it is a WHO question. The most commonly used standard format for a User Story creation is stated below:

As a <user role/customer, I want to do so that I can.

Example:

As a WhatsApp user, I want a camera icon in the chat write box to capture and send pictures so that I can click and share my pictures simultaneously with all my friends.

(b) Acceptance Criteria (i) Given (a context) (ii) When (an event) (iii) Then (an outcome)

User stories: (1) Used in Agile Methodology (2) Less detailed (3) It is logged onto the JIRA tool (4) Relatively faster (5) Format: (a) As a WHO I want WHAT So that WHY (b) Acceptance Criteria (i) Given (a context) (ii) When (an event) (iii) Then (an outcome) (c) Supporting Models

8)Agile:

1) What is Jira

2)Terminologies in Jira university example Epic--university stories--physics, biology, department Task Bug framework hai scrum and kanban board also sprint min 2 week se maximum 4 week tak ka hai.

3) workflow in : Jira To do, In progress, To be verified(Test) Done

4) Example of membership of Epic, registration as stories with create registration as a task

5) Go to the Atlassian site and register for 14 dys trial with Jira and Scrum board.

Planning 6)roadmap--->creation of epic and about that user stories -->start to end roadmap batayaga backlog---user stories will be seen here and on the right side by creating a sprint, adding the user stories to the sprint board, and then starting the sprint by giving time and date. board ---here u will see board kan /scrum jaise to do in progress wala waise manage workflow to change workflow

9 What are Scrum Roles?

Product Owner à The Product Owner presents to the stakeholders and manages and prioritizes complex projects, particularly in software development. They follow Agile principles. Scrum Master à Facilitates the Scrum process, removes any obstacles for team performance, and ensures adherence to Scrum principles. Development Team à is a self-organized team responsible for delivering the product increments

What is meant by a User story and user point in Scrum?

1. User Stories: User stories are brief descriptions of a feature or functionality written in a user-centric format. They capture the user's role, the desired feature, and the benefit it provides. User stories promote collaboration and understanding between the development team and stakeholders.

2. Story Points: Story points are a relative measure used to estimate the effort required to complete a user story. They represent the complexity and size of the work. Story points are assigned based on the team's collective judgment, using a scale like the Fibonacci sequence. They help in planning and prioritizing tasks and provide a basis for measuring the team's productivity and velocity.

https://www.youtube.com/watch?v=FTE1bKMAZfI&t=112s--mukta test plan. https://www.youtube.com/watch?v=ritM8Sm-6tA&t=4s---mukta jira video.