Skip to content

Update README.md #1

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.

Sign up for GitHub

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

Open
paulinabustos wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update README.md #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0b875b4
Update README.md
paulinabustos Feb 24, 2018
bd43899
Adding rules
paulinabustos Feb 24, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 24 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,5 +14,27 @@ The old linear method of software development deals with change poorly. A key co
### Define the Problem, not the Solution
First, define the actual problem. Rather than prescribing a solution, share as much as possible your understanding of the problem your agency is trying to solve. This could be:
- CA residents are taking too long to fill out
- we have low engagement on our website
[TODO]: add more examples
- We have low engagement on our website
- Our users do not complete the process on time
- Our users' experience with the site is poor rated

### Define metrics, not releases
Real agile do not rely on arbitrary release dates but on iterations based on how the product is growing. To start a real agile process define metrics and based the roadmap moves according to those metrics.

### Describe your users
An Agile teams knows its users as they know themselves, provide user profiles and users references into the RFO. Team should be eager to know your users.

### Explain your current solution as a process
Software never ends, it is a process that moves continously. Define the extension of your process and let the team explain how they will divide and conquer.

### Describe the policies you HAVE to follow as CONSTRAINS
Agile teams that work with governments know that there are laws and policies to follow. You should always describe them in your RFO and be sure to ask the teams to describe how they will tackle them.

### Allow for an open proposal
Instead of giving a hard template for creating a proposal allow teams to use their formats. This will allow you to evaluate creativity in their teams.

### Ask for the development process and not specific roles
An agile team knows their team is as strong as their weakest member. Teamwork is important for an agile team and this should be represented in their development process. Don't ask for specific roles, ask about the tools and process used inside the team.