Everyone at ZibaSec is part of a team, which means we work together. We take advantage of our collective knowledge, experience, and diverse thinking to do the best possible work we can. To facilitate high collaboration and avoid working in silos, we have a single ‣ for our organization. All work is tracked here, from every department.
This list is prioritized. The most important thing to do next, for the whole organization, is always at the top in Next Up . We work on tasks in chunks called cycles.
The task list is ordered by the leadership team, and like everything we do, is open to questions and feedback. If you feel that a task item could be better represented, you're encouraged to bring your reasoning up in a discussion, private message, or Slack channel.
A task can range in size and scope from a bug fix to a full-blown project. It will always include a general description of the goal, the reasoning and intent behind the task, and a time estimate of the scope. These are purposefully high-level, low-fidelity items, and they are not meant to be step-by-step instructions.
Cycles are what we call blocks of time spent working on one or more tasks. They help us to scope and coordinate task items.
We're experimenting to find a regular cycle length. At the moment, we're trying out 4-6 weeks per cycle.
For more on how task cycles work:
Choose the next highest task item that suits your skillset. Assign yourself to it by filling out the People field.
<aside> 💡 If the top priority item isn't in your usual wheelhouse but seems like something you'd like to challenge yourself with, talk to the task creator about taking it on. We believe wholeheartedly in knowledge sharing and building your skillset, so if it's feasible to make that happen, we will!
</aside>
Depending on the task, you might work on it by yourself, or you might pair up with a team member for knowledge sharing or to divide and conquer. We'll decide this on a case-by-case basis. If you assign yourself to a task and later decide you'd like some support, talk to the task creator and we'll make it happen.
If a task needs to be broken down into smaller parts, divided between team members, or if you have questions about how it might be executed, engage in these discussions in Notion. This helps us retain a clear history of the decisions we make.
Write out your thoughts in the task page, and leave questions and comments on someone else's writing using Notion's features.
For technical tasks, use the task page as needed to write out thoughts and plan your approach. Create GitHub Issues in the appropriate repositories as required to complete the task. Add links to the Issues in the Task List.