Your team is already overworked and when launch time approaches, the client comes to you with important request.What do you do? How do you approach your team ?
Your team is already overworked and when launch time approaches, the client comes to you with important request.What do you do? How do you approach your team ? Saving Changes...
You need to define the importance of the request and whether this importance needs to be incorporated into this release or it can wait till the next release if its a software development cycle. Clients expect some push back from their Project Managers in order for them to ascertain if they really need a particular requirement. Saving Changes...
Nilesh KulkarniEnterprise Agile Coach| ThoughtworksPune, India
I see as 2 problems.
1)
Team is overworked - work with client and see how we can play with the triple constraints and solve it. Team is which is stressed out may not be doing a great job even for current scope of work.
2)
client ask for important feature - look at what is remaining time and what is remaining scope. can you swap new feature with the old one? can you change the dates? any other options? Saving Changes...
Lonnie PacelliAuthor & President| ProjectManagementAdvisor.comBellevue, Wa, United States
Be cautious about tripping at the finish line with last-minute changes. Each change should absolutely go through some form of a change control board with a question of "what is the worst thing that happens if this change isn't implemented at release?" If there is a true regulatory or policy change that needs to be implemented then that may require you give serious consideration, but you want to truly understand the "absolutely must haves" versus the "nice to haves". Saving Changes...
