Module 1 Practice 2: Managing Your Time and Stress

Group 1

 

Case

As a team lead you are responsible for your team delivery and the project overall.

During the night (time zone difference 10 hrs), your customer sent you emails with different important request such as strange system behavior on production,

questions to the sprint features implementation, upcoming features  feasibility analysis, upcoming regression testing plan,

and asked “Why is dev environment not stable and shows error?”. In addition, you have your own sprint commitments.

What do you do?

 

Get back to the customer as soon as possible with a quick reply/updates and let him know that we are on top of those issues and have been starting looking into them (Might be just a short reply, more details can be sent tomorrow during the day after having done some investigation procedures).

1

Prioritize, evaluate, handover, support, and debrief issues.

Those steps would include:

  • prioritizing issues according to the level of urgency
  • evaluating to identify what can and should be delegated
  • handovering important issues to make progress on them immediately by communicating clear expectations about the goals of the tasks, resources that will be provided, the timeline and proper level of autonomy
  • support issues during resolution process and monitor the status

2

At the end of the day regardless of the investigation results, customer should be informed about results. (Summary of work that have been done during the day and results)

4

Set up the meeting with the team to discuss incoming issues, actions plan, and answer questions. (Communicate clear expectations about the goals of the tasks and the timeline).

Note: actions plan from step

 

3

2

Issue prioritizing






 





 






 

DO FIRST

DO LATER

DELEGATE

ELIMINATE

strange system behavior on production

 

sprint features implementation (clarify with the dev team)

upcoming features  feasibility analysis(dev team involved)

upcoming regression testing plan(dev team involved)

 

own sprint commitment

investigation of strange system behavior on production

investigation stability on dev env

check feature fesability from the aplicaton architecture side

testing plan

 

 blocker for product usage and spoil the overall impression

has direct impact on the progress right now and might be needed to clarify some questions to reduce unnecessary work
during the sprint and still be on track and follow clear expectations from both side

THANK YOU

Q&A

Made with Slides.com