A single team process framework for managing product development

Is a software development method based on frequent delivery cycles

Kanban in lean manufacturing is a system for planning inventory control and replenishment

1. Scrumban is an agile method originally designed as a transition method between Scrum and Kanban

2. It is another hybrid agile framework and method that evolved by itself, where teams use Scrum as the framework and Kanban as the process improvement method

Developed to meet the specific needs of large-scale software development projects

1. is an agile project delivery framework

2. Known for emphasizing constraints to drive delivery

3. The framework sets cost, quality, time from the outset and then leverages formal scope prioritization to meet these constraints

Is a branch of the Unified Process (UP) in software projects

1. Crystal is a family of methodologies

2. The Crystal Methodology is designed to quantify and provide options for methodological rigor based on project size (the number of people involved in the project), as well as the criticality of the project

1. Lean concept

2. The relationship between Lean, Kanban and Agile

Also known as "meta Scrum"

Is a technique used by two or more Scrum Teams rather than one large Scrum Team, where a team includes three to nine members to coordinate its work

Hold regular meetings

Provides a knowledge base for all levels of the enterprise to carry out large-scale development work

It is a framework for organizing multiple development teams with the common goal of extending the Scrum method.

1. It is a process decision-making framework that integrates multiple agile best practices in a comprehensive model.

2. DA aims to balance popular approaches that are too narrowly focused (like Scrum) or too detailed (like AgileUP)

1. Is a framework designed to apply the Scrum methodology through a more holistic organizational layer rather than a single product development layer

2. The aim is to extend agile methods beyond project execution by enabling disruptive innovation

Deliver value, respect people, reduce waste, be transparent, adapt to changes, and continue to improve

toyota

pull system

Once the team completes an item, it can pull another item into the process

Provides the development team with a convenient mechanism to organize work

It also allows the development team to see at a glance how much work is left.

burn down chart

Comparison with other plans

Holistic

Lead time

Backlog size

Remaining to-do items

period time

Work in process quantity information

Work in progress

Number of tasks completed

Completion statistics based on different modules of Kanban

Determine scope changes and trends for current projects

Centralized office

the whole team

A well-informed workplace

real customer engagement

team continuity

sustainable rhythm

pair programming

test first programming

incremental design

Shared code/collective ownership

Code and test documentation

Refactor

user stories

weekly cycle

quarterly cycle

jet lag

Root Cause Analysis

tailoring team

Pay as you use

Negotiate Scope Contract

Daily stand-up meeting

10 minutes to build

continuous integration

Test first

Single code base

incremental deployment

Daily deployment

work together

one writes code

a real time review

Be more focused and efficient

Break down team barriers

develop new skills

Caves and common areas

fish tank window

remote pairing

They are all communication technologies and methods that may be used in distributed teams