How to manage tasks when sprint ends ?

Project Manager_w3mmyj

For product development our organisation has been following this structure:

1. task assigned to developer >
2. Developer reviews the tasks and once done assigns it to code reviewer (seniors) >
3. Once code is reviewed it is deployed on pre-production server for QA to review >
4. Once QA passess the task it is deployed in production server

 

So the problem is that we have say 20 tasks that one of our client needs as features in our product so that we can deploy it for them. Out of these 20 tasks we plan to take say 10 in first sprint (2 weeks). And we keep a pre-production version say pp-v1 as our target (remember this deployment is yet to be sent to QA as per above flow.

 

Now once the sprint is completed we have say successfully completed 8 out of 10 tasks and pushed them on pre-production server.

 

My question is that at this stage do we close these 8 tasks ? Even though they are just pushed on pre-production ? If not then do I keep them open and let them spill to next sprint as they are not completing the workflow till we meet the live-production ?

 

If we spill the tasks to next sprint we will also have issues with velocity don't you think? How do you suggest we manage this ? Please elaborate with examples.

 

Thank you.

Petter Gonçalves

Hello Chirag,

There are several options that you can use to manage the "concluded" issues in the pre-prod environment. Personally, I think the most coherent way that will better display in your reports would be to:

- Configure a new separated project to handle all the pre-prod tasks

- Perform the development and implementation steps in the First Sprint (Steps 1 to 4)

- Close the tasks in the sprint once they are moved to pre-prod

- Once the tasks are in pre-prod, create new linked tasks in the new project you created so it can be tracked until it reaches the Live-prod environment

Usually, the team that will work and gets feedback during the pre-prod experiment is not the same persons who developed the tasks, so this is the option used by most of the customers I have spoken so far in order to better track the pre and post-production details and get feedback separately in two projects.

Let me know if it makes sense to you.