Scrum and motivation -
When it comes to making work time, how can you prevent the Dev team from pading their numbers?
Vs
P>
Whenever we will reduce the scope, quality or increase the resources
The foundation is trusting the best method But why do not you put them in the first place? If you think that they are not for work, then it is not better to start the project because it is almost certainly unsuccessful for failure - either because you are right and the team is a group of inept developers, or because you Wrong, but lack of trust and more control makes the team scope and in reality their commitment and enthusiasm worsens.
OTOH If you are sure that you have made the best available to the people, and that they are talented and motivated, then best give them a good challenge, let them work and all Try to overcome obstacles.
In most of my experience, most developers start with enthusiasm and are motivated to create products that they can be proud of. However, impossible timelines, rhetorical expectations, too much bureaucracy, control over management and last but not least, reducing quality - can quickly kill that inspiration.
The issue of tight practices is that developers are right to estimate / estimate the cost of a specific feature if the management projects allocated resources, scope, and time of both It is almost always in disaster, if OTOH developers are given trust and responsibility, then they will generally rely on work. In the scrum, problems arising during Team Sprint / fights problems / issues get together. In one of the best projects, team members are soon imprisoned with the team and they feel personal responsibility for the project. It can be done until the team is poked to the leggie members to produce results instead of pulling it back.
Comments
Post a Comment