1. Individuals and interactions over processes and tools

2. Working software above thorough documentation

3. Customer cooperation takes precedence over contract negotiation

4. Respond to change better than follow plan

1. Continuous delivery, small steps and quick steps

2. Embrace change and improve your strengths

3. Provide early feedback and value ranking

4. Achieve results and measure progress

5. Continuously updated to strengthen agility

6. Streamline products and eliminate waste

7. Teamwork, daily interaction

8. Trust members and give support

9. Face to face communication, efficient and clear

10. Members from all parties, stable rhythm

11. Work together and organize yourself

12. Team introspection and continuous improvement

1. Number of people: 3-9 people

2. Team members are cross-functional and T-shaped talents are encouraged

3. Members need to be full-time, and at least they cannot change at will within the iteration.

4. Have the authority to make any form of decision within the constraints of the team charter/iteration backlog

5. High degree of self-organization ability

6. Need to demonstrate product functionality to Po

7. Team needs to define DoD

1. Determine product features

2. Decide on release date

3. Prioritize user stories

4. Responsible for product ROI

5. Before each iteration/sprint, adjust features and priorities as needed

6. Accept or reject the work of the development team

7. As a spokesperson for customers, receive different needs and feedback, and constantly sort out the to-do list

Titles within different organizations

team facilitator

Purpose

type

Responsibilities

1. Information emission source

2. Visualization: display project status and transparent information of all parties

3. Ensure continuity of workflow and value delivery

4. Contains: work to be done, work in progress, completed work

5. Comply with Work-in-Progress (WIP) limits: It’s more important to finish work than to start new work

1. Lightweight development process

2. Customers and developers face-to-face

3. practice

2 to-do items backlog

Category 3 personnel

4 meetings

Time BoxTime Box

Hand over work to the next duty station at the end of each day

1. Establish long-term video conferencing links between locations

2. Open the link at the start of each day's work

3. Close connection when work is finished

Two people are paired up to work on the same job, sharing screens via tools

Use three factors to determine the right approach for your project

1. Organizations cannot be fully agile

2. Agile transition period

3. Accelerate forecast lifecycle delivery speed

4. Change team members’ thinking patterns

1. Add more iterative techniques to promote learning

2. Adding more incremental technologies accelerates return on investment for sponsors

3. Try the new technology first on a project with low risk and low-to-moderate uncertainty

4. After successfully using hybrid methods through the organization, before trying more complex agile projects

Introduce your product in 1-2 minutes to arouse interest

1. Demonstrate project features and the benefits they bring

2. Has a name and brand

3. Includes how-to guide

1. Team values: sustainable development speed and core work hours

2. working agreement

3. basic rules

4. team norms

1. is a sorted list

2. PO is responsible for content, availability, priority

3. always incomplete

4. is dynamic

1. Detailed and brief appropriately

2. estimated

3. Dynamic development

4. Prioritize

1. Team members should first consider doing a demo

2. No adjustments are made within a sprint

3. Bugs in this cycle do not necessarily have to be resolved in this cycle. It depends on the priority of the bug and needs to be confirmed with the PO.

4. Product Backlog takes into account design and requirements

5. Sprint Backlog takes into account both planning and design

what was accomplished yesterday

What are you going to do today

What difficulties and obstacles did you encounter at work?

Part 1

Part 2

Specific steps

1. Team demonstrates the developed product functions to PO

2. PO organizes meetings and invites stakeholders to participate

3. Through live demonstration

4. No need to be too formal

5. PPT is not necessarily required

6. Generally controlled within 2 hours

7. Attribute judgment, not variable judgment

8. If the user story is not passed, the PO determines the priority and determines in which sprint it will be completed.

1. also called reflection meeting

2. The purpose is to summarize experiences and lessons to facilitate further problem solving

3. Fishbone diagram and card method can be used

4. Hamburger principle: Praise first, then criticize and then give solutions

5. Evaluating change: Reflecting on why it changed and how to avoid it

6. Evaluation of unfinished user stories: why they were not completed

7. one thing rule