Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How do you fit retrospectives into Kanban projects

The company I have just started working for has decided that they want to move away from using Scrum to using Kanban to run their software projects.

Although I can definitely see the benefits of Kanban in their situation, I'm very keen to make sure my team carries on running retrospectives to ensure continued improvement, and to improve team moral.

Has anyone found a good way of fitting in retrospectives in Kanban projects?

1 comment

The most effective method I saw was that the team created a "story" which named a release.  That story could only be dealt with by getting the team together, having a retrospective to look at all the issues in the "done" column, and at the end of that meeting, clicking "release"


Log in or Sign up to comment

Atlassian Community Events