Agile Projects at Work Agile Customer Collaboration in Everyday Work

Agile Customer Collaboration in Everyday Work

Agile Projects at Work

tags
  • # about
  • # advise
meta
  • Length
    355 words
  • Reading Time
    1 min 11 sek
  • Create
    Engineer
    Advise
    20%
    20%
    80%
t.o.c.
With projects.kalbeck.com, kalbeck.media provides a key tool for the distribution of tasks and prioritization of processs in agile projects.
Depending on the type and the structure of the project kalbeck.media chooses an agile project management approach where it makes sense and is applicable. A key tool for that is projects.kalbeck.com.

The Process at a Glance

1. Initial Briefing


Clarifying the Requirements
  • The project and its environment are defined in the workshops

2. Definition of User Stories


Describing the Tasks
  • Requirements are defined from the user’s perspective
  • The formulation of the user story includes the perspective, the desired goal, and the resulting value – that means “As a [role] I want to [goal] so that [value], e.g. “As a user I want to be able to log on the website so that I can see limited content”
  • User stories are divided into domain-specific tasks, depending on the individual user story in fields such as backend, frontend, design, interaction, and communication
  • Efforts for the respective tasks are estimated by the team

3. Creation of the Backlog


Compiling the Task Overview
  • The customer prioritizes the user stories
  • The user stories are arranged in the backlog according to the customer’s prioritization

4. Classification in Sprints


Starting the Development
  • A sprint describes a development step towards an evaluable interim result
  • The sprint is equipped with a total score that corresponds to the available resources
  • The user stories from the backlog are transferred from the backlog to the sprint until the total score is exhausted – and thus the available resources
  • The customer can adapt the sprint before the start if necessary
  • The sprint starts and the team works on the specified tasks

5. Sprint Review


Rating the Results
  • After the sprints have been completed, the customer receives the results of the user stories
  • The customer accepts the partial result
  • Feedback and new ideas can be generated from the result and may influence the next sprint

The Software


kalbeck.media uses the project management platform projects.kalbeck.com for the control and implementation of agile projects. projects.kalbeck.com is based on Taiga.

Too long; didn't read


Depending on the type and the structure of the project kalbeck.media chooses an agile project management approach where it makes sense and is applicable. The process at a glance:

  1. Initial Briefing: Clarifying the Requirements
  2. Definition of User Stories: Describing the Tasks
  3. Creation oft he Backlog: Compiling the Task Overview
  4. Classification in Sprints: Starting the Development
  5. Sprint Review: Rating the Results

The project management software projects.kalbeck.com is based on Taiga.

Related Articles

The customer as a colleague

Agile Project Collaboration as a Trump

Agile project management involves the customer as an active collaborator - as an enabler, feedback provider or input giver. Rapid development cycles and technological progress require processes that lead to the best possible solution .

About Us

kalbeck.media hautnah

The best ingredients made to measure – for results to individual tastes.
All done by the digital manufacturer in the heart of Vienna .

Your first time

Startups & Innovation Engineering

Mediocrity in life is boring. Mediocrity in business is fatal. Startups have to stand out and make a difference - kalbeck.media is able to start them off.

Clients

Extract from the customer portfolio

From strategy consulting to technical implementations. From software engineering to print-ready corporate design. This is where you can find an extract from our credentials- presented as the obligatory logo wall of fame.