Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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
4,465,237
Community Members
 
Community Events
176
Community Groups

What Agile scheme type for production and implementation environment

We have a production and implementation environment. We noticed that working with sprints is not efficient, because the tasks move from spint to sprint while the task to do brings more complexity and subtask associated with. Also production environment generates tickets that takes time away from us for the coordinated tasks.

what schema of agile should we use?

1 answer

0 votes

Hello @Diego Galan ! Welcome to the Atlassian Community!

IN GENERAL, it sounds like you have a lot going on!

If I read this right, you are responsible for releasing new functionality (set up as tasks) while at the same time doing support in the production environment.  That sounds like your teams are drowning in a lot of work!

A few things to ponder before we talk about Scrum vs. Kanban:

1. Does your team have a good idea of the things that need to be done before the task is accepted into the sprint?  It sounds like they don't and are finding out that it's too much, which means it keeps moving to future sprints.

2. Does your team have an idea of its capacity?  This usually may come from story point velocity or number of t-shirt sizes.  How do you know your team has an appropriate load?

3. This capacity is definitely being affected by the unplanned work (the production tickets).    What's the nature of the unplanned work?

Scrum looks at delivering work by the end of the sprint.  To do this, teams have to have an idea of how much work they can take.  If there is confusion and creating of subtasks during the sprint, the work is not clear or it's too big.  Your team should look at breaking it up.

If you move to Kanban, that may not be a "magic solution" because you have a lot of unplanned work coming in.  You have to make sure that your team can focus otherwise they'll be drowning (like they are right now!)

Tell me more about how your team is planning their work, estimating effort, and judging their capacity.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events