Yellow Squad Wiki Home

Slogan for public consumption: Go go Golden Horde!

Slogan when we feel tired: Go go Yellow Banana Slugs!

Current project is LEP/ParallelTesting .

Weekly review call checklist

Briefly review where we are in project plan.
Any new tricks learned?
- Collaboration tricks?
- Debugging tricks?
- Communication tricks?
- Checklists? Processes?
Any nice successes?
- Can you attribute your success to anything beyond the innate brilliance of yourself and your coworkers?
Any pain experienced?
- Questions to ask:
  - Are there any cards that are/were taking too long to move?
    - Are they blocked?
    - Are we spinning our wheels?
    - How long is too long?
  - Are we not delivering value incrementally?
  - Are we not collaborating?
  - Did we duplicate any work?
  - Did we have to redo any work?
    - Did we misunderstand the technical requirements, the goal, or a process?
    - Was the ordering of tasks that we chose broken?
- Can we learn from it?
  - Checklist?
  - Experiment?
  - Another process change?

Not buildbot with Juju. Jenkins? Net positive, but in future question directives? Have time associated with answering that question, when we propose? Kind of like agile.

Next "new to us" project (like charms) when we do not know enough to write tests initially, we want to try this process:
- Prototype (no tests, as a rule)
- Squad discussion: lessons learned, design decisions
- Begin coding, TDD.
We will read all ~yellow reviews when in feature development.
We are interested in using Go for our next project, if appropriate.
Short term goal: charm is ready for review next Tuesday, Feb 14. We would like to provide feedback to the juju team about our experience, and we are willing to take time to do so. Gary is reaching out to hazmat and SpamapS to see how it would be best to do this.

How will we share smaller design decisions that we learn during the day? The daily call is good but not good enough. IRC? micro-blogging?