Agile work is based on a principle to Minimize Work In Progress. The tasks are pulled by the team members rater than pushed by management. Agile teams are empowered and self-managed, and requirements are often only high level (user) stories about desireable features - specific on what but not on how. We need to get our heads around this - how can this be effective? …is it even efficient?

Context

This module is developed in the context of PBA programme for IT Architecture Copenhagen School of Technology and Design (KEA). It’s part of the fulfillment of the curriculum of the topic Agile Development.

The Tech Stack

We will be exploring the following technologies:

GitHub Projects
Trello Boards
MarkDown
Kanban
Scrum

Learning goals

Understand and master tools and techniques to support agile planning.
Understand Kanban Boards and Scrum Boards - how they differ and how they match.
Establish a joint portfolio - of agile stuff!
Understand spike, timebox, kaizen blitz.

Prepare for class

The class is now redefined as a team (not a class, not a group, not an organization or a department - but a team! Something entirely different!).

Now we need team tools - and your preparation before the class is to Sign up and introduce yourself:

Join a Trello organization (their lingo for team) and join a GitHub team.

IT Architects @ KEA - Team 2022

Trello

Use this link to join an organization on Trello
Then use this link to join the “Portfolio” board
An finally use this link to see the template card

Click “Create card from template” Copy over lists and labels - put the card in the “Members” list and work the five task from the list.

GitHub

Accept this assignment in GitHub Classroom
Open the repository shown to you in the process and work the two tasks described in the README.md.

Resources

📚 2: Scrum/Kanban difference
⏱️ [15:00] (read time), 📺 [11:00] (three embedded videos)

We touched briefly on KanBan earlier. The method is old (1980’ies) - it derives from “TPS - Toyota Production System” - Lean Manufacturing. To many it’s seen as an alternative method to Scrum. Luckily Kanban is merely a technique and Scrum is (sometimes) a methodology - not (always) a religion - so you are free to combine them if you got the stomach for it.

Watch Atlassian’s take on Kanban - and Miro’s explanations of the difference between KanBan and Scrum.

What are your thoughts? any preferences?