Agile Concepts

[KD]

Sprint Retrospective Meeting happens at the end of the sprint after sprint review meeting. It will be attended by product owner, scrum team and scrum master. it will be held for 1-2 hours. Here the team has to answer three questions,
1.   What went well in this sprint?
2.   What did not go well?
3.   What are the required areas of improvement for next sprint?

[12127176011]

The sprint retrospective is more about the scrum team feedback on sprint- Once we have done with the sprint review meeting then the sprint retrospective meeting scheduled to discuss what went well, what went bad, what are the improvement areas for the next sprint.

Whereas, a sprint review meeting is more about the sprint, whether the developed solution meets the client requirement or not. 

[12102149910]

What is a retrospective?

It is a recurring meeting after every sprint to discuss what went well and what can be improved.

[12102149610]

SCRUM can be implemented either at the beginning of the project or when you sense that project is falling behind schedule. This model exercises full admin power.

[12215200701]

Retrospective is meeting held by a scrum to discuss on

1) What went well in the Sprint
2) What can be improved
3) What has to improve in the next Sprint

[12107163810]

Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Agile methods or Agile processes generally promote a disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices intended to allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals. Agile development refers to any development process that is aligned with the concepts of the Agile Manifesto. The Manifesto was developed by a group of fourteen leading figures in the software industry and reflects their experience of what approaches do and do not work for software development. Read more about the Agile Manifesto. Did you know that Agile can also be applied to hardware projects? Learn about Cprime?s revolutionary Agile for Hardware framework.

Get more information and Mural templates to get started with Agile

[12107170810]

Those who don?t learn from the past are doomed to repeat those mistakes in the future. This concept has been preached by many in a variety of disciplines, and product development is no exception.

In an agile environment, the focus is primarily on quickly getting releases out the door and worrying about what?s next, so there often isn?t a lot of discussion of what?s already in the rear view mirror. An agile retrospective forces the entire team to pause and reflect on what transpired and discuss what worked and what didn?t during a particular project.

The meeting format is key to an effective retrospective since the value comes from the conversation and dialogue, not just a bunch of individual statements. A representative from each group should be present (if not, everyone involved), with each person given floor time to share their view of the experience. This can include marketing, sales, customer service, and operations representatives as well.

Although pointing out the flaws and problems encountered is important, participants are equally encouraged to bring up the positive aspects as well. The meeting should be considered a safe space for bringing up contentious issues and contrarian views for it to be as productive and insightful as possible.

These meetings are often led by product management as they?re the most cross-functional role in the organization and have a broader view of what happened during the project. However, an impartial third-party of facilitator can also be used to ensure everyone is treated equally and given a fair share of floor time

[12118184212]

An agile retrospective, or sprint retrospective as Scrum calls it, is a practice used by teams to reflect on their way of working, and to continuously become better in what they do.
The whole team attends the retrospective meeting, where they ?inspect? how the iteration (sprint) has been done, and decide what and how they want to ?adapt? their processes to improve.  The actions coming out of a retrospective are communicated and done in the next iteration. That makes retrospectives an effective way to do short cycled improvement.

The retrospective facilitator (often the Scrum master) should have a toolbox of retrospective techniques, and be able to pick the most effective one. Some of the techniques to do retrospectives are asking questions, state your feelings with 1 word, 5 times why (Root Causes) or asking why, Agile Self-assessment Game, solution focused/strengths and retrospective of retrospectives.

WHY to take retrospectives
So if you want to solve the problems that you are having, and deliver more value to your customers, you have to change the way you do your work. That is why agile promotes the usage of retrospectives: To help teams to solve problems and improve themselves!

[12203215802]

This happens at the end of the sprint where team will answer 3 question.
1. What went well in the sprint?
2. what did not go well?
3. What are the required areas of improvement in next sprint ?

[12120171211]

An agile retrospective is an opportunity for agile development teams to reflect on past work together and identify ways to improve. Agile teams hold retrospective meetings after a time-boxed period of work is complete (typically a sprint lasting two to four weeks). During the retrospective, the team discusses what went well, what did not go as planned, and how to make the next work period better.

[12130164810]

Sprint Retrospective Meeting happens at the end of the sprint after sprint review meeting. It will be attended by product owner, scrum team and scrum master. it will be held for 1-2 hours. Here the team has to answer three questions,
1.   What went well in this sprint?
2.   What did not go well?
3.   What are the required areas of improvement for next sprint?

[12117192212]

Sprint retrospective meeting:- This meeting will be conducted for an hour at the end of the every sprint to retrospect & improve at the end of the every sprint to retrospect & improve further for the next sprint.

In here the team will be answer 3 questions:-
1.What well in the sprint.
2.What did not go well.
3.What are the required areas of improvements in  the next sprint.