I would like to bring up my story for a closing project to have a discussion on practice as a Scrum Master.
At that time I am working as a member in the Development Team roled as a support Engineer and Scrum Master in the Scrum Team for the offshore team. One day I have received the notice that, the project will be closed and Scrum Master (as Server Engineer as well), designer and the other Engineers will not be in the team anymore except me.
The remaining goal for the current project will be notified the users that the project will be closed. Actually the team now composed of Product Owner, me and one Engineer in the offshore team. The Product Owner asked me to provide a plan for the remaining time.
Since the team size is far less than what the guidelines mentioned and the goal is clear that the remaining part will not have changes. I have suggested to the Product Owner to do the followings:
- Close the current sprint, move all the unfinished tasks back into the Product Backlog archived as Lesson Learned.
- Adopt Waterfall approach for the remaining time, and breakdown the tasks required to fulfill the goal.
- Keep daily standup to make sure there will have no impediments for the remaining tasks.
- Sprint retrospect will be held on the project closing date and deliver that to the Product Owner.
To my opinion, this is what I can do for the time to keep up with the responsibility for the remaining tasks done. I would like to bring up a discussion to see what you will do if you were me.