Scrum Sprints in Kribik: Everything You Need to Know

Welcome back! Following our introduction to managing projects with Kribik, let's dive deeper into leveraging Scrum sprints to maximise productivity and efficiency. If you've heard terms like "Scrum," "Sprint," or "Scrum Master" but aren't entirely clear on their meanings, this guide is for you.

Key Roles in Scrum Sprints

Before we dive into creating and running sprints, let's clarify some essential roles:

• Product Owner (PO): Responsible for prioritising tasks based on business value and user needs.

• Scrum Master: Facilitates meetings, helps resolve team blockers, and ensures smooth workflow.

• Developers and Designers: Responsible for completing tasks and delivering functional increments of the project.

• Project Manager (optional): Ensures the project's overall goals, timelines, and resources are effectively managed.

What if you have a small team?

For smaller teams, these roles can overlap or be shared. For example:

• In a team of programmers, one person might act as both Scrum Master and Product Owner.

• A solo programmer might fulfil all roles, using Scrum methodology to structure their personal workflow.

What is a Scrum Sprint?

A Scrum sprint is a fixed time period (usually two weeks, though it can vary) during which specific tasks from your project backlog are selected, planned, and completed. Think of it as a clearly defined goal-setting period that helps your team stay focused and consistently deliver value.

Planning and Executing Scrum Sprints in Kribik

Here's how you effectively plan, execute, and track Scrum sprints using Kribik:

1. Sprint Planning Meeting:

   • Gather your team to select tasks from your project backlog.

   • Clearly define and estimate each task's complexity and time requirements.

2. Creating the Sprint in Kribik:

   • Navigate to your project's dashboard and click "Create New Sprint."

   • Enter a descriptive name (e.g., "Sprint 1 – User Authentication").

   • Set the sprint duration (typically 1–4 weeks).

   • Drag tasks directly from the backlog into your sprint.

3. Using the Kanban Board in Kribik:

   • Clearly visualise task progress through columns such as "To-Do," "In-Progress," and "Done."

   • Move tickets between these columns as work progresses.

4. Daily Scrum Meetings (Stand-Ups):

   • Hold brief (approx. 15-minute) meetings daily.

   • Team members briefly state:

     • What tasks were completed yesterday.

     • Tasks planned for today.

     • Any blockers or challenges they are facing.

Tracking and Resolving Blockers in Kribik

Blockers are issues that prevent progress. In Kribik, blockers can be flagged by:

• Adding comments directly to the relevant ticket.

• Tagging the ticket as "Blocked."

• Discussing during daily stand-ups to quickly resolve issues.

Completing a Sprint: Review and Retrospective

When a sprint finishes, hold two essential meetings:

• Sprint Review:

  • Showcase completed work to stakeholders or the Product Owner.

  • Move unfinished tasks back into the backlog or future sprints.

• Sprint Retrospective:

  • Discuss as a team what went well, what could be improved, and concrete actions for future sprints.

Why Kribik is Ideal for Scrum

Kribik provides comprehensive tools such as integrated Kanban boards, clear sprint setups, effortless task tracking, and built-in communication channels—perfectly aligning with Scrum practices.

Next Steps

You now have a solid understanding of how to leverage Scrum within Kribik, whether your team is large, small, or even just you! Continue exploring and adapting your workflow, and stay tuned for more tips and guides.

As always, we welcome your feedback and questions!