A document containing test cases for the current sprint

A set of done user stories

A shippable increment

Positive customer feedback

Following the plan

Velocity chart

Working software

No documentation, just User Story format is enough.

Need necessary documentation, like business workflow, and wireframe for better communication.

Yes, they need to send weekly updates to business.

problem-solving, product teams discover problems and needs through user interaction, with user stories as placeholders for conversations, not order taking on the requirement

build a big plan and follow the plan on time, on budget, and within the scope

Just-in-time Resolution, Analysis upfront has a small scope – just enough to get a pilot started. Impediment resolution happens frequently.

focus on customer-centric, what to deliver and why. Not focus on solution/system how to build at the beginning.

It's another format of requirement

A defect logged by a product manager

A card that includes a short, simple description of a feature for conversation and confirmation

A task from the development team

Not deploy the product as plan

Develop the wrong product which doesn't delivery value for the customer

Over budget

The delivery speed is not fast enough

Scrum Master

Project Manager

Scrum Product Owner

Daily Scrum

The team leader (Scrum master) should allocate the specific tasks to individuals

Tasks should be randomly allocated to team members

A team member should self-select tasks appropriate to their skills

The most complicated tasks should be allocated by the team leader

Stay FOCUSED on the important things

PRIORITIZE your work

give TRANSPARENCY to the company

EVALUATE individual performance