Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,457,706
Community Members
 
Community Events
176
Community Groups

How do you fit retrospectives into Kanban projects

Gemma Wooden
Gemma Wooden Oct 08, 2018

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?

Comment
Watch
Like Be the first to like this
573 views

1 comment

Nic Brough -Adaptavist-
Nic Brough -Adaptavist- Community Leader Oct 08, 2018

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"

Like
Reply

Comment

Log in or Sign up to comment
Agile
TAGS

Atlassian Community Events

See all events