What is Agile(able to move quickly and easily.
) - The Agile methodology is a way to manage a
project by breaking it up into several phases. It involves constant collaboration with stakeholders and
continuous improvement at every stage. Once the work begins, teams cycle through a process of
planning, executing, and evaluating.
What is Scrum
Scrum is a specific Agile methodology that is used to facilitate a project. Scrum is a framework
that helps teams work together. AGILE and SCRUM is not same. Scrum is just one of the frameworks by
which you can implement agile.
------
How do you calculate productivity in Scrum?
Productivity can be measured by velocity, i.e. the number of story points you delivered
in a sprint. If you delivered 20 story points in 2 sprints, then your productivity is 10 story
points per sprint. I would not recommend tracking effort in hours. Instead, be focused on your
goal and put the effort into achieving it.
====
How many hours is productive in Agile?
My experience is that an agile team that has an average overall utilization of 65% is generally
working pretty productively. That means that in an 8 hour day, a team member who is at 65%
utilization is accomplishing somewhere between 5 and 6 hours of focused effort every day.
=====
======
Agile Methodology in Software Development and Testing,
Agile Testing,
Agile Scrum Process,
Scrum Methodology with Scrum Team and Scrum Master.
---------------
AGILE - able to move quickly and easily. HYPERLINK "https://www.scrum.org/resources/what-is-
scrum"
What is Scrum?
https://www.scrum.org › what-i...
HYPERLINK "https://translate.google.com/translate?hl=ta&sl=en&u=https://www.scrum.org/
resources/what-is-scrum&prev=search&pto=aue" மொழிபெயர்
Scrum is a lightweight framework that helps people , teams and organizations to work together to
generate value (result) through adaptive solutions for complex problems.
- Scrum teams use story point estimation
RALLY VS JIRA
Agile is a project management philosophy that utilizes a core set of values or principles.
Both RALLY and JIRA are focused on Software development
RALLY main focus on Development
We split the story (which actually creates a parent and another child) then Rally will automatically
split the completed and incomplete tasks.
JIRA for software development for medium and large scale project. Because it supports and flexible
for Procurement of many projects
Select the appropriate reason for splitting a story, and then type an explanation for it. Click Split.
I think RALLY works on days counting 8 hours a day
JIRA works on STORY POINT in hours
Both are capable of handling 10 users
The whole cake is a cake and each vertical slice is a piece of cake with all it's layers.
- JIRA has access to both Kanban and Scrum templates
REMOVE STORIES FROM SPRINT
First sprint she can’t be changed. In order to maintain this,if you want to change sprint by adding user
stories or removing, while the sprint is running, the backlog items you change need to be an
equivalent size.
When should you split a user story?
Ideally, a story should be finished in 2 or 3 days. If you're not able to confidently say it can be done in
that time slot, then you need to split it.
Great User Stories are like pictures. When you look at them a story unfolds.
What happens to incomplete stories in Sprint?
Whenever your team finds an incomplete story at the end of the Sprint, simply roll that story,
in its entirety, into the next Sprint. When this happens, no points should be awarded to the team, for
partial completion of the story
Dealing with Stories That Roll Into the Next Sprint - Fully re estimate the story in to the whole from
the scratch
What happens with incomplete sprint backlog items?
"All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog. The
work done on them depreciates quickly and must be frequently re-estimated.”
When should the product backlog for a sprint be refined?
I like to hold the product backlog refinement meetings three days before the end of the current
sprint. This gives the product owner sufficient time to act on any issues that are identified.
Who owns backlog in scrum? Who prioritises sprint backlog?
the product owner
What are 3 C's in user stories?
Whether you are a newbie or a seasoned veteran, the 3 C's of User Stories help keep the purpose of
the user story in perspective.
The first C is the user story in its raw form.
How often should work remaining in Sprint Backlog be tracked?
According to the Scrum Guide, "The Development Team tracks this total work remaining at
least for every Daily Scrum to project the likelihood of achieving the Sprint Goal".
, the Card. ...
The second C is the Conversation. ...
The third C is the Confirmation.
What is SCRUM Team?
A scrum team is a group of collaborators, typically between five and nine individuals, who work
toward completing projects and delivering products. The fundamental scrum team comprises one
scrum master, one product owner and a group of developers. Within a scrum team, there is no rank
or hierarchy.
who decides sprint length
The ScrumMaster is ultimately the one who gets to choose a team's sprint length. A good
ScrumMaster will do everything possible to arrive at a consensus. But, when the ScrumMaster
exhausts his or her collaborative, facilitative skills without arriving at a consensus, the good
ScrumMaster makes the decision.
Hours vs STORY POINT
- hourly base
8 hours base development
STORYPOINT
Based on complexity of the story. Varies by whether we worked on this before, was it from the
backlog as to know we have some knowledge already on this story, completely a new story, do we
new to analyse this story
How long should a 5 point story take?
For 2 story points, the number of hours might need 3 to 4 hours. For 3 story points, the number of
hours might need 5 to 10 hours. For 5 story points, the number of hours might need 10 to 15 hours.
Ideally, a task should not take more than 16 hours ie 2 story point
Scrum defines several events (sometimes called ceremonies) that occur inside each sprint: sprint
planning, daily scrum, sprint review, and sprint retrospective (The sprint retrospective is a recurring
meeting held at the end of a sprint used to discuss what went well during the previous sprint cycle
and what can be improved for the next sprint.).
The main agile scrum artifacts are product backlog, sprint backlog, and increments.
The Product Backlog contains all the items in the software development project. The Sprint Backlog
contains only the items of the Backlog specific to the current Sprint.
who decides sprint length -SCRUM MASTER
Scrum board vs Kanban: Basic Definitions
Scrum boards are more methodical but require more prep time and organization; Kanban boards give
team members more leeway, but don't provide the same level of organizational structure like SCRUM.
Scrum
Scrum can easily be considered to be the most popular agile framework. The term ‘scrum’ is much
considered synonymously to ‘agile’ by most practitioners. But that is a misconception. Scrum is just one of
the frameworks by which you can implement agile.
The word scrum comes from sports rugby. Where the players huddle together in an interlocked position
pushing against the opponents. Each player has a defined role in their position and can play both offensive
and defensive as per the demand of the situation.
Similarly, the scrum in IT believes in empowered self-managed development teams with three specific and
clearly defined roles. These roles include – Product Owner (PO), Scrum Master (SM) and the
development team consisting of the programmers and testers. They work together in iterative time
boxed durations called sprints.
The first step is the creation of the product backlog by the PO. It’s a to-do list of stuff to be done by the
scrum team. Then the scrum team selects the top priority items and tries to finish them within the time box
called a sprint.
How to Practice Agile?
However, the most popular methodologies amongst all of them are:
Scrum
Kanban
Lean
Extreme Programming
Kanban
Kanban is a Japanese term which means a card. These cards contain details of the work to be done on the
software. The purpose is visualization. Every team member is aware of the work to be done through
these visual aids.
Teams use these Kanban cards for continuous delivery. Just like Scrum, Kanban is also for helping the
teams work effectively and promotes self-managed and collaborative teams.
But there are differences between these two as well – like during a scrum sprint, the items being worked
upon by a team are fixed and we cannot add items to the sprint whereas, in Kanban, we can add items if
there is available capacity. This is particularly useful when the requirements change frequently.
Similarly, another difference is that while the scrum has defined roles of a PO, scrum master, and
development teams, there are no such pre-defined roles in Kanban.
Another difference is that while the scrum suggests a prioritisation of product backlogs, Kanban has no such
requirement and it is totally optional. Thus Kanban requires less organization and avoids non-value adding
activities and is suitable for the processes which require responsiveness towards changes.
Lean
Lean is a philosophy that focuses on waste reduction. How does it do that?
In lean, you divide a process into value-adding activities, non-value adding activities and essential
non-value adding activities. Any activity which can be classified as a non-value adding activity is a waste
and we should try to remove that wastage in the process to make it leaner.
A leaner process means faster delivery and less effort wasted in tasks which don’t help to achieve the team
goals. This helps to optimize every step in the software development cycle. That is why the lean principles
were adapted from lean manufacturing into software development.
An Agile retrospective is a meeting that's held at the end of an iteration in Agile software
development. During the retrospective, the team reflects on what happened in the iteration
and identifies actions for improvement going forward.
RETROSPECTIVE MEETING
An Agile retrospective is a meeting that's held at the end of an iteration in Agile
software development. During the retrospective, the team reflects on what happened in the
iteration and identifies actions for improvement going forward.
What are the 3 retrospective questions?
Three things you can do today
What went well (keep doing these things)
What could be improved (went OK, but could be better)
What went badly (don't do these things again)
Focus for next period/sprint/month/quarter (One or two things to focus on)
