“As a network administrator, i want the ability to update the timeout value in application configurations remotely through a management portal”
If this is a SaaS deployment and you feel that it has a good value add for the admin consumer, it looks like a good story. But if you have one enterprise application and you want to help your network admin by building this feature it might not be a good value for money.
How do you explain this to developer, without a closed door meeting?
If you are following agile, work as a team. Don't hide facts and numbers. One simple number that your team should be knowing is the cost of running one sprint. When i say cost, it the cost to company to manage X team members for Y days. Say your cost per sprint is $30K and your velocity is 30 points, it will be roughly 1000$ for a story point ( you may as well argue that it will not be so proportional, neither the story points.)
Now look back at the story point one would give for the story mentioned, if team decides as 5 points - its good 5K. Now decide, will you educate the system admin to do this manually or go back and write an application to do it for 5K?
Once the team understand the cost aspect, you don't really have to explain about the ‘cost of poor quality’ to team.
No comments:
Post a Comment