Working in an environment like Cloud Foundry with agile development, pair programming, testing, and more, you may find yourself asking many questions about what the Cloud Foundry ideals are, and why they are. There are many answers to these questions, and every developer has their own answers. The following are some questions you may be asking, and should be able to answer by the end of your dojo program. If you don't feel ready to answer these questions, your pair is a great resource to hear their thoughts and gain their perspectives. You may even wish to pose the same question to multiple pairs to see how different people think differently about these core ideals.
Keep in mind, we have intentionally omitted the answers to these questions.
- Why do we pair? Why is it valuable to the team? Why is it valuable to me?
- Why do we rotate so frequently?
- How do I leave feedback for my pair?
- What kind of feedback can and should I leave for my pair? What does "ASK" mean?
- Should newer team members only pair with experienced team members? Why?
- When should I drive? When should I navigate?
- What should I do if my pair is driving too much? Not enough?
- How can I stay engaged if my pair is moving too quickly?
- How quickly should I be ramping up?
- What do we get out of an IPM?
- Why do points matter?
- Why is the "P" in "IPM" not "Pointing"?
- How well should I understand a story before I'm ready to point?
- Everyone else seems to understand the story. Should I assume my pair will fill me in when we pick it up?
- How do we decide how many points a story is worth?
- Why do we have standup?
- What information is worth sharing?
- Why is it more valuable to talk about today's upcoming work than yesterday's accomplishments?
- Why should we not push code when the build is red?
- What is continuous integration, and why do we do it?
- What is the value of retro? Why is it weekly?
- How do tests improve our confidence in our code's correctness?
- Why test driven development instead of writing tests second? How do tests help inform our design?
- Do all correctly-written tests provide value? If not, what are examples of tests that do not provide value?
- Why do we value short feedback cycles? What are examples of short feedback cycles in our process?
- What is an iteration (it's not just a week at work)? How is it different from a sprint?
- Which story should I start working on? What should I do if I don't know how to implement the first story in the backlog?
- What is an MVP? Why do we focus on the "M"?
- What does velocity measure?
- How does your product manager use velocity?
- How does velocity compare between teams?
- How is product direction determined?
- How are stories prioritized?
- What is the role of user research in product?
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent