Shaping
Cycle
Pitch
100

which are the Shaped work 3 characteristics?

It’s rough, It’s solved, It’s bounded

100

name at least 1 reason why a 6 weeks cycle is reccommended

It is long to create sw and short to see the deadline from scratch
it allow us to discover at first and then still have enough to develop value

100

within the Pitch, in which section are fat marker sketches usually used?

Solution

200

Who shapes?


1 or 2 Product Leads  and maybe someone else.

200

What are the kickoff meetings for?

to ask questions that aren't clear in the documentation

200

The noGOs are...

Functionality or use cases we intentionally aren’t covering

300

Shaping output is supposed to be concrete? or abstract?

Neither. or Both.

300

What are the kickoff meetings for?

to ask questions that aren't clear in the documentation

300

when the DevTeam has to gets access to the Pitch?

after the bet has been decided and the pitch has been selected for the cycle

400

What is the Appetite, and how it is related with the batch concept?

Appetite is How much time we want to spend in the solution. A big Batch projects demands all 6-week cycle dedicated. a small batch project don't.

400

when a cycle can be extended?

when the remaining needed scopes are in the downhill

400

a Rabbit hole is

a technical tricky situation where the team might fall and keep falling forever that is addressed in the pitch with a way to avoid falling in it

M
e
n
u