Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Play #4 - Add "Value" as an outcome #188

Open
eharrisSSA opened this issue Aug 3, 2016 · 1 comment
Open

Play #4 - Add "Value" as an outcome #188

eharrisSSA opened this issue Aug 3, 2016 · 1 comment

Comments

@eharrisSSA
Copy link

I'd like to recommend adding some information pertaining to value to this play. We're trying to focus more on becoming product-minded vs project-minded, and one of the differences is focusing more on the value a project adds instead of focusing on the date it will be delivered, the way we do today. Not that the iron triangle isn't important, but we often loss focus on the customer by focusing solely on dates. The Standish Group add value as a factor of success in 2015.

Is it possible to add something related to value in both the checklist and key questions.
For example: Checklist - Run tests or experiments to ensure solution provides value to the customer (or agency).
For example: Key Question - What was the value added? Or - What goals/outcomes can we expect to receive? Something that focuses more on the outcomes instead of the outputs.

Thanks for the consideration.

@rebelwarrior
Copy link

Value seems a bit of a vague word for the playbook and seems you have a very specific context in which you use it. I mean delivering by a date has a value as well. I definitely think there is confusion on the word agile and many people seem to associate it with speed rather than adabtability to rapid change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants