SCRUM with KANBAN
during the iteration ,if the project already under development stage and at the med of the iteration the product owner want to freeze the project till unknown date ,what is the correct action for this project ,should we keep it under development or change it back to product backlog or delete it .
Is the Sprint Goal commitment still valuable, or has the Product Owner determined that it is now obsolete?
Personally, I don't like the status 'On Hold'. Either something is actively being developed, or it must compete with the other backlog items.
What action is taken on a specific ticket depends on the situation. Why did the Product Owner freeze the ticket?
For example:
- If he needs some clarifications and expected changes he can delete (or better cancel for documentation reasons) it until he creates a new ticket for the new scope.
- If the PO just want to change priority the ticket should go back to the backlog and needs new refinment for the remining work (but changing priority during an iteration ..... . It must have very very good reasons!)
- ...
the PO ask the SCRUM team to stop all the development and hold them until further notice due to unexpected challenges related to Financial part ,so this project need to postpone until unknown date ,our concern is related to the opened projects that reflect in the DevOps tool ,should we move them to backlog or keep them under development ,and who is the responsible to take the decision ? also who is responsible to move the project in the system in this case
- What is the Scrum Team now doing in the meantime, since all development has been stopped?
- I suspect that the last Sprint has ended already, so all the Sprint Backlog Items that haven't been finished should be returned to the product Backlog.
- Sprint Backlog Items that meet the acceptance criteria (DoD) and have been accepted by the PO and Stakeholders are normally a part of the Increment.
- For point 2, this can be done by anyone of the Scrum Team SO LONG the Product Owner is informed of this (PO stays accountable for the Product Backlog)
- For point 3: It will be up to the DevOps Engineer/GIT Responsible (or whoever this is in your company) to park the codebase of the Increment.
6. What has this problem to do with "Scrum with Kanban"?
if I am properly reading between the lines, I say shifting to Kanban with a backlog of techdebt to help the team improve tooling/product/monitoring... would be the right move. This way you are better ready when the business come back with a vision/roadmap/workitems.