search

cfpb / agile-playbook

https://github.com
Creative Commons Zero v1.0 Universal
5 stars 4 forks source link

First draft of values statements #1

Open mistergone opened 9 years ago

mistergone commented 9 years ago

My first draft is over in my repository. I would love some comments and feedback before I make a PR!

https://github.com/mistergone/agile-playbook/blob/master/README.md

@stephanieosan @andybacon @ascott1 @elizbond @marteki

Scotchester commented 9 years ago

before I make a PR

:no_mouth:

:stuck_out_tongue_winking_eye:

mistergone commented 9 years ago

Before I uh... well... uh... technically I typed that before I made the PR. :octopus::question::question:

marteki commented 9 years ago

I agree with @virtix that it'd be good to add references to the Agile Manifesto. I might go further, and also add references to things about Scrum and Kanban and other stuff that's influenced the way we practice Agile at the CFPB. Another way to subtly call out that we incorporate lots of things, and aren't rigid in our mindset or practice.

mistergone commented 9 years ago

@marteki I totally agree that we need to talk about Scrum, Kanban, etc - those are things I intend to include in a second, more technical document about implementation of frameworks. :smile:

Eventually, this will all be compiled into a nice github pages website. This first README is just the introduction and values statement.

marteki commented 9 years ago

:+1: :smiley:

stephanieosan commented 9 years ago

I'd like to see us speak more directly about how these principles are put into practice across our teams. It seems like you touch on this in many places, but maybe each principle should have a "what this looks for our teams" type of section.

For individuals, maybe it's worth talking about how we empower each of our teams to adapt and customize how they work and communicate to best fit them.

For customer collaboration, I'd mention that we prefer close working relationships with our clients where representatives of different parts of the Bureau serve as product owners, and we often have embedded subject matter experts and content specialists within our tech teams.

I think it might be worth highlighting how ingrained iteration based on user feedback is to our process, and how much we value usability testing and user research. Maybe that fits best under the Responding to change heading. Working agile-ly allows us to pivot when we realize that what we're building isn't working or needs changes to make it better serve consumers.

mistergone commented 9 years ago

For anyone watching this PR, I moved the values out of the README into its own doc (in ./_pages/, which is basically kind of a "in case we use Jekyll sometime" directory name). The values doc should be linked from the README now. :octopus: