Lire avec attention le livre "Shape Up - Stop Running in Circles and Ship Work that Matters"

[stephane-klein]

J'ai déjà parcouru plusieurs fois le livre Shape Up - Stop Running in Circles and Ship Work that Matters.

Le but de cette issue est de lire avec sérieux ce livre.

Todo :

• [ ] Introduction
• [ ] Part 1: Shaping
  • [x] Principles of Shaping
  • [ ] Set Boundaries
  • [x] Find the Elements
  • [ ] Risks and Rabbit Holes
  • [x] Write the Pitch
• [ ] Part 2: Betting
  • [x] Bets, Not Backlogs
  • [ ] The Betting Table
  • [ ] Place Your Bets
• [ ] Part 3: Building
  • [ ] Hand Over Responsibility
  • [x] Get One Piece Done
  • [ ] Map the Scopes
  • [ ] Show Progress
  • [ ] Decide When to Stop
  • [ ] Move On
  • [ ] Conclusion
• [ ] Appendices
  • [ ] How to Implement Shape Up in Basecamp
  • [ ] Adjust to Your Size
  • [ ] How to Begin to Shape Up
• [ ] Glossary

[stephane-klein]

Élément qui m'interpelle et m'intéresse (from) :

Shaping is a closed-door, creative process. You might be alone sketching on paper or in front of a whiteboard with a close collaborator. There’ll be rough diagrams in front of you that nobody outside the room would be able to interpret. When working with a collaborator, you move fast, speak frankly and jump from one promising position to another. It’s that kind of private, rough, early work.

[stephane-klein]

Intéressant (from) :

First, we need to have the right people—or nobody—in the room. Either we’re working alone or with a trusted partner who can keep pace with us. Someone we can speak with in shorthand, who has the same background knowledge, and who we can be frank with as we jump between ideas.

Ceci va à l'opposer "de la mode" de la "coconstruction", "brainstorming"…
Personnellement, j'adhère à cette méthode.

[stephane-klein]

Rhhh ! J'ai envie de m'acheter une tablette graphique Wacom Intuos S pour faire des wareframe à gros train 🙄.

[stephane-klein]

Section qui attire mon attention (from)

Decentralized lists

We don’t have to choose between a burdensome backlog and not remembering anything from the past. Everyone can still track pitches, bugs, requests, or things they want to do independently without a central backlog.

De ce que je comprends, bien que les auteurs de Shape Up conseillent de ne pas maintenir un "vrai" backlog, ils laissent la liberté aux membres de l'organisation de gérer des "backlog" décentralisé.
Si je comprends bien, elles ne sont pas officielles.
J'aime bien l'idée, cela pourrait résoudre des problèmes que j'ai rencontrés dans des jobs précédents :thinking:.

[stephane-klein]

Je trouve ceci très très pertinent, je pense la même chose (from)

Rather than delegating to a separate build team, our senior people make up the team. David (CTO) takes the programming role and works with Jason (CEO and designer) or a senior designer with Jason’s guidance. This is necessary for two reasons. First, you can’t delegate to other people when you don’t know what you want yourself. Second, the architectural decisions will determine what’s possible in the product’s future — they define the “holes” that future features fit into. At this phase the team needs to hold the vision of the product and be able to judge the long-term effects of design decisions.