Great Development Teams

Get Started. It's Free
or sign up with your email address
Great Development Teams by Mind Map: Great Development Teams

1. Roadmap + Scrum

1.1. A spec DOES NOT have all the answers

1.2. Minor course corrections along the way

1.3. Hard to have failure states

1.3.1. No Black box

1.3.2. Harder to be genius in the lab

1.4. Team engaged with the product

1.4.1. IMPORTANT: Operational phase of measure and iterate It's living

2. 2. Some Failure states

2.1. Not seeing the big picture

2.1.1. Connect to business

2.1.2. Think about people as well as code Code is law You make the rules e.g. Mick testing one of my applications e.g. Pressing 'Back' on a form

2.2. Genius in the lab

2.2.1. Enforcing own coding principles Boost? English language methods or tightly compressed strings?

2.2.2. The need for perfect architectures

2.2.3. Black Box Problem Request goes in, feature comes out - perhaps

2.2.4. Refusing to integrate into a process

2.3. Multiple sources of truth

2.3.1. The evil spreadsheet Jay's spreadsheet

2.3.2. Evil email Jared's inbox

2.4. Fear

2.4.1. Fearing to say you're stuck

2.4.2. To be seen as bad, lazy or slow Over promising creates a team of failures

2.4.3. Fear of leaving comfort zone Throw yourself at it and see what happens

2.5. Not aligned on focus

2.5.1. Sub-optimal project planning How does the team decide what is in this sprint? How are decisions made in realtime?

2.5.2. Confused customers

2.5.3. Poor realtime decision making

2.5.4. DEFINE: Knowing the end objective. Small sets of clustered functionality. Measurement and iteration

2.5.5. Velocity alignment with business Going too fast Make problems for later Going too slow because... Too perfect Too scared Unclear focus Overwhelmed

2.6. ? Observations in your team?

3. 4. A squad needs a process

3.1. Automate Automate

3.1.1. Unit testing

3.1.2. Automated releases

3.1.3. Continuous integration

3.1.4. Jason Hoffman: Joyent Failure to administratively scale Werner Wogels: Amazon: 80% crap 20% creation inversion

4. 3. Serve the business

4.1. Know the roadmap

4.1.1. Startups Runway thinking Leads to focus

4.2. Know the objective

4.2.1. Why are people selling what we build a certain way? Where do we change how/what we build? Where do we educate the rest of the business?

4.3. Communicate out

4.3.1. Educate how the parts connect

4.3.2. The entire business is responsible Help everyone else engage with you

5. 1. Pre-Amble

5.1. Background

5.1.1. Kazaa 300 million users / 5 million concurrents Team in 5 countries Significant security threats / hackers Legal battle

5.1.2. Pollenizer 40 startups Everyone has the same problems Most have insufficient process

5.2. Today - What I have seen of great teams