![]() ![]() I am going to focus mostly on how to manage date pressure within your team and not talk about how to push back on dates. The intent of this post is to give some strategies that all teams should be able to execute on, no matter what dates senior leadership pushes on you. Today, I was reviewing a promotion document and found something very concerning. The promotion document was written by an SDE I attempting to move to SDE II, completely in their own words. On all four example projects, they had the same central theme the project was challenging because of the time pressure in delivering the project quickly. An immediate red flag went off in my head. When a developer believes all of their projects are being impacted by time crunches and lists that as one of the top challenges, the team is in a bad place. I am writing this article as a warning on how the constant pressure to deliver can destroy a team and what I do to combat it. I am no stranger to the constant stream of delivery dates and the constant stream of getting one feature launched just so you can move on to the next. I am a manager at and have been in that role for about 6 years. ![]() Disclaimer:I'm not representing Amazon in any way with my posts, opinions written here are strictly my own. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |