Skip to content

Latest commit

 

History

History
126 lines (77 loc) · 3.79 KB

OPERATIONS.md

File metadata and controls

126 lines (77 loc) · 3.79 KB

Operations

These are the working arrangements for The Spark. Please PR to improve!

Daily

On a daily basis we aim to perform the following tasks:

Async updates

Add an async update to The Spark's slack channel #w3dt-the-spark. Prefix the message with ⚡️ to differentiate it from other messages.

Weekly

Every week we do the following:

Demo time

We attend a private w3dt "demo time" every Friday @ 17:00 UTC (09:00 PT) (Sign up form). Most recorded demos are published to slate and YouTube:

Demos should be 5-10 minutes.

This enables full focus on Tue/Wed/Thurs, hopefully yielding something to show by Friday.

Planning

We have a planning meeting every Monday @ 16:00 UTC (08:00 PT). We'll not record these, but they're publically available for anyone to join.

Planning on Monday helps us focus on the right things to do for the week.

We use a HackMD notepad for collaborative meeting notes. An issue is opened on the repo after each meeting with a new a notepad URL for the next. After each meeting the notes document is added to the team repo.

Async prep:

  1. List of things you shipped 🚢 (NOT everything you worked on - this is done throughout the week async. It is FINE to not have anything in this section).
  2. List of things you're blocked on.
  3. Proposals for things to work on next.
  4. Add the project(s) you're working on to the list for discussion.

Meeting notes template:

# The Spark Planning YYYY-MM-DD

## Agenda

1. Async updates: participants broadcast their own async update and answer any questions.
2. Current projects: review and assign tasks for the next week.
3. Project pitches: review status and next steps if there are changes.
4. Open discussion for any other questions that arise.

## Async Updates

@name
- 🚢 Shipped:
    - Ship0
- ⛔️ Blocked:
    - Blockage0
- ⏭ Next:
    - ProposedNextStep0

## Projects

Stages key:

1. 💡 Researching/pitching
2. ⏳ Evaluating (Pitch PR sent)
3. 🚜 In Progress (Working on project)
4. 🤝 Handover/feedback (Submitted back to customer)
5. ✨ Complete
6. 💾 Paused and saved for another day

### Current Projects

Planning for the projects we're actively working on.

#### Project Name (stage) (@champion)

**Goals:**

* Goal0

**Tasks:**

@name
- Task0

### Pitches

Projects we're writing up or have written that we may work on in the future.

* Project Name (stage) (@champion)
* ...

## Notes/Questions

General notes and/or questions go here.

In the meeting we:

  1. Congratulate each other on the things we ship 👏.
  2. Determine ways forward for blockages.
  3. Discuss each project and it's next steps (the plan for the week).
    • This might be a case of copying over proposed next steps to the relevant sections, but we may decide to alter the course as we discuss.
  4. Answer any questions that come up.

General

CoLo

We have a (virtual) colo room open 24/7 for team members to use for sync chats.

Project Pitch/Project work

Aim to allocate up to 50% of your time to pitches (this includes research) and the remainder to actual project implementations.

Project work should not take > 4 weeks.

Scratch space

Each member has a home directory in the repo they can use for notes/code/whatever. You're encouraged to use this space as much as possible.