Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

Great Development Teams by Mind Map: Great Development Teams
5.0 stars - 1 reviews range from 0 to 5

Great Development Teams

Roadmap + Scrum

A spec DOES NOT have all the answers

Minor course corrections along the way

Hard to have failure states

No Black box

Harder to be genius in the lab

Team engaged with the product

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

2. Some Failure states

Not seeing the big picture

Connect to business

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

Genius in the lab

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

The need for perfect architectures

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

Refusing to integrate into a process

Multiple sources of truth

The evil spreadsheet, Jay's spreadsheet

Evil email, Jared's inbox


Fearing to say you're stuck

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

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

Not aligned on focus

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

Confused customers

Poor realtime decision making

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

Velocity alignment with business, Going too fast, Make problems for later, No time to document, No time to automate, No time to test, Going too slow because..., Too perfect, Too scared, Unclear focus, Overwhelmed

? Observations in your team?

4. A squad needs a process

Automate Automate

Unit testing

Automated releases

Continuous integration

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

3. Serve the business

Know the roadmap

Startups, Runway thinking, Leads to focus

Know the objective

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?

Communicate out

Educate how the parts connect

The entire business is responsible, Help everyone else engage with you

1. Pre-Amble


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

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

Today - What I have seen of great teams