Zum Haaptinhalt sprangen

Roadmap

Below is a concise description of how we plan and execute our work throughout the year. It is intended for clients and partners who wish to have an overview of our quarterly approach, our two‐week sprints, and how we manage PI (Program Increment) Planning two weeks before the end of each quarter.

Roadmaps

Check out our roadmaps to get an overview of our current priorities and our vision for the year.

Current Quarter Roadmap
Discover the features and targeted priorities for this quarter.
Current Year Roadmap
Get a comprehensive view of our objectives and key points for the entire year.

Why Is This Important for You​

  • Transparent milestones: You will know exactly when sprints start and end, and when the major planning events (PI Planning) take place.
  • Regular check-ins: Each sprint includes a review (or demo) meeting where you can see progress, provide feedback, and request adjustments.
  • Proactive end-of-quarter alignment: Organizing PI Planning two weeks before the end of the quarter allows us to easily adapt to the priorities of the following quarter without rushing.

Working Together​

  • Stay involved: Your feedback during sprint reviews and planning sessions guides our decisions regarding features, fixes, and priorities.
  • Anticipate: With milestones set every two weeks (for sprints) and each quarter (for PI Planning), you can adjust your own business or release deadlines accordingly.

Overview of Work Items​

AI Smarttalk manages two major types of incoming work items:

  1. Features – New features or improvements to existing ones.
  2. Bugs – Defects or issues within existing features that require a fix.

Below is a quick overview of how features and bugs typically progress through our process:

Item TypeReview TimingTypical Priority FlowPlanning Cadence
FeaturesBiweekly prioritization reviewsAccepted (to backlog) / Postponed / RejectedDetailed during PI Planning (every 3 months)
BugsContinuous triage; critical bugs analyzed as soon as possibleHotfix (if critical) / Bugfix (if less critical)Can be inserted into the current or next sprint

Annual Plan – Overview​

We divide the year into four quarters (Q1, Q2, Q3, Q4). Each quarter typically spans three months, and we use two-week sprints to break down our work. This approach ensures:

  • Regular updates according to a predictable schedule.
  • Frequent feedback loops, where you can share your ideas and steer the project.
  • Adaptability in case priorities shift mid-quarter.

Key Milestones​

  1. Sprints (every 2 weeks)

    • We conduct a series of two-week sprints throughout the quarter. Each sprint concludes with a review of the work completed and planning for the next steps.

  2. PI Planning (2 weeks before the end of each quarter)

    • Two weeks before the end of each quarter, we hold a PI Planning session.
    • Why 2 weeks before? This schedule allows us to gather sufficient information, user feedback, and team availability to finalize the objectives for the next quarter without disrupting the final sprint.

  3. Quarter Transition

    • At the end of each quarter, we compile the findings from sprint reviews, incorporate the latest feedback, and prepare the objectives for the next quarter.

How a Quarter Typically Unfolds​

A quarter (for example, Q1, from January 1 to March 31) consists of 6 sprints of approximately 14 days each. Here is the typical schedule:

  1. From Sprint 1 to Sprint 5 – Normal development cycles, each lasting two weeks.
  2. PI Planning – Held around the fifth or sixth sprint, approximately two weeks before the end of the quarter.
  3. Final Sprint & Closure – We use the final sprint to finalize deliverables and address any outstanding issues. At the end of the quarter, you have a clear view of completed features, resolved issues, and upcoming steps.
  • Q1 spans from January 1 to March 31 (approximately 90 days).
  • Q2 spans from April 1 to June 30, etc.
  • Each quarter includes a milestone (PI Q1, PI Q2, etc.) two weeks before the end of the quarter (e.g., Q1 ends on March 31, PI Q1 is scheduled on March 17).

Note: This structure (6 sprints per quarter, each 2 weeks long) may vary slightly depending on the actual calendar, holidays, or specific project needs. Nonetheless, the biweekly sprint cadence and the PI Planning before the end of the quarter remain constant to provide you with predictable milestones.

Glossary​

Info

Below is a glossary of terms commonly used in our development methodology:

Sprint​

  • Definition: A period of time (typically 1 to 2 weeks) during which the team focuses on a set of objectives (user stories, tasks) to deliver a functional product increment.
  • Objective: To enable rapid iterations, frequent visibility into progress, and the ability to adjust at the end of each sprint.

PI (Program Increment)​

  • Definition: A longer time interval (often a quarter, ~8 to 12 weeks) that groups multiple sprints.
  • Objective: To plan and align teams on broader strategic objectives, while allowing for adjustments on a longer timeframe than a sprint.

Backlog​

  • Definition: A prioritized list of features, improvements, and fixes to be implemented. It is maintained by the Product Owner or the product team.
  • Objective: To ensure that the team focuses on items that deliver the highest value to the product or project.

User Story​

  • Definition: A concise description of a feature from the user's perspective (“As a [user type], I want [capability] so that [benefit]”).
  • Objective: To focus on user value and clarify functional requirements.

Epic​

  • Definition: A large-scale user story that is generally decomposable into several smaller stories.
  • Objective: To manage and structure complex features or large-scale projects.

Release​

  • Definition: The delivery of a stabilized version of the product to the production environment or to users.
  • Objective: To provide usable value and gather concrete feedback.