- Platform for Economic Inclusion
- Preference Editing Tools Design
- Fluid Infusion
- Design Handbook
- Social Justice Repair Kit
- BIG IDeA
Agile development is a software design and development methodology that advocates having many, short iterations throughout the life-cycle of the project. Fluid's agile planning process uses 2-week iterations, where all the work is planned at the beginning of the iteration. At the end of the iteration, how much work was actually completed is compared to what was planned (velocity), and this information helps determine how much work to plan for the next iteration.
both within the design team and across the community
Encourage & enable frequent conversation
about status of work, priority, roadblocks, what we are learning, what has changed, etc.
Reflect on what we know & priorities
through the "planning game" that kicks off each iteration
Focus during iterations
new requests, needs, changes, etc. become part of the next iterations "planning game" to allow us to stay out of reactionary mode
Make mistakes faster
we learn from mistakes so the sooner we know about them the sooner we can build our depth of knowledge and correct where needed
Create a comfortable place to share ideas
no idea is a bad one; we want people to feel comfortable sharing design ideas with early and often and know they can expect to get the right level of feedback.
to kick off each iteration, the team gets together to:
Meant to be short & simple meeting. This meeting happens everyday (or at consistent intervals) at the same time. In a shared environment, everyone stands to remind people the meeting is short we can decide if this makes sense for us. Each participant has a chance to answer to 3 questions as we go around the room. The questions are:
Any other questions are typically handled outside the stand-up in follow-up conversations as-needed.
via phone, IM, breeze, email between team members
we will maintain a "status board" to demonstrate work progress to ourselves and the community. The board includes:
How do we do this in the digital world? My experience has been with index cards hanging on the wall and colored dots to show status.
A Pig is someone who has skin in the game. Mike Cohn aptly refers to the people in that role as, "Having their Bacon on the line." Pig roles are considered core team members. Performers. People who "do" work.
A Chicken is someone who has something to gain by the Pigs performing, but in the end, really do not contribute day to day to "getting things done." Their "eggs" are a renewable resource, and many get laid.