Eric's Leadership Methodology

1. Development Process

1.1. Story Mapping

1.2. Scrum or Kanban

1.3. Iterative Development

1.4. Personas

1.5. Tools

1.5.1. Whiteboard

1.5.2. Post-It Notes

1.5.3. Markers

1.5.4. Mind Maps

1.5.5. Trello

1.5.6. VersionOne

2. Engineering Practices

2.1. Continuous Integration

2.2. Automated Deployment

2.3. Automated Testing

2.4. Test-Driven Development

2.5. Domain-Driven Development

2.6. Pair Programming

2.7. Collaborative Team Space

3. Recruiting

3.1. Create Compelling Team Environment

3.2. Performance-Based Interviews

3.3. Coding Auditions

3.4. Existing Team Gets Veto Power

4. Training

4.1. Clean Code

4.2. Object-Oriented Principles

4.3. Service-Oriented Principles

4.4. Test-Driven Development

5. Motivating

5.1. Factors

5.1.1. Purpose

5.1.2. Mastery

5.1.3. Autonomy

5.2. Servant Leadership

5.2.1. Providing Clear Vision

5.2.2. Removing Impediments