Overview

This page catalogues all of the current tasks for the Software Team, divided across all of our major efforts. We use a Jira/Scrum style organizational structure to track work, with 2 Week Sprints, and stand-ups at our weekly Software Meetings.

Procedure

Unless otherwise specified, all tasks in the backlog are up for grabs. However, you must talk to @Sandhya Moorthi before starting on a task, to ensure you have a sufficient understanding of the requirements, and resources to complete this task. Neglecting to do so will make work significantly more difficult, or impossible to use if done improperly.

Tasks have hard deadlines by when they must be completed by, and points which indicate the expected time to complete. A buffer exists between the two to accommodate unexpected issues.

<aside> ⚠️

Within our project, many deadlines are set by external partners (Pleiades, Air Force Research Lab, and other external collaborators). Failing to complete tasks on time rarely ONLY causes delays: it can jeopardize our mission success, and significantly impact Satellite Lab’s reputation.

When taking on a task, you are agreeing to complete it by the specified deadline. Tasks which are not completed will be reassigned promptly.

If you have any questions, concerns, or issues which may delay work on a task, please reach out ASAP.

</aside>

Tags and Attributes

For those who may be unfamilar, the following is a quick refresher of the attributes you can see on individual tasks.

Status

The status of a task indicates where it is in the workflow:

Status Meaning
Backlog Task has not been started yet and is available to be claimed.
In Progress Task has been claimed, is actively being worked on.
Review Under review for merge or integration.
Done Task is fully completed.
Archived Task is no longer active or eligible to be worked on.

Points

The rigor and time commitment of a task:

Status Meaning
1 1 week time commitment, can be completed over a weekend.
2 2 week commitment, multiple days of work, check-in at software meeting.
3 3 week commitment, may take more than 1 Sprint to complete.
4+ Individual tasks should not be this big, and should be broken up accordingly.

Ground Station Middleware

Description & Goals: Initial Ground Station Software Tasking

Untitled

Flight Software Development

Untitled