SLS Software Department

Commencez. C'est gratuit
ou s'inscrire avec votre adresse courriel
Rocket clouds
SLS Software Department par Mind Map: SLS Software Department

1. diagram

2. SDLC

3. Sprint 82 Review

4. How to Request Software?

4.1. As part of a project with a signed off work package:

4.2. Create a user story

4.2.1. [as a] Specific Role [i want] The ability to do something [in order] to achieve some business value/benefit

4.3. What is a Product Owner?

4.3.1. Rob, Dave and John

4.3.1.1. CSPO

5. About the team

5.1. About JP

5.2. <5 years experience

5.2.1. Number of software developers have doubled every 5 years consistently.

5.3. Our Team

5.3.1. >200 years of software experience

5.3.2. averaging 17 man years of expereince

5.3.3. target 14 strong

6. About Software

6.1. The Three Rules

6.1.1. Structured Programming 1968 (banning the go-to)

6.1.2. Object Oriented Programming 1966 (banning Messing with other peoples data)

6.1.3. Functional Programming ~1968 (banning changing any data)

6.2. Democratizing SW

7. Why Agile Software Development?

7.1. Complexity

7.2. What is Agile?

7.2.1. Main Diagram

7.2.1.1. More Detailed Diagram

7.2.2. Characteristics

7.2.2.1. Value

7.2.2.2. Ability to Change

7.2.2.3. Visability

7.2.2.4. Risk

7.2.2.5. The Pigs and Chickens

7.3. Agile Sprint In Action

7.3.1. Sprint 72

7.3.2. Burn Down

8. Products

8.1. Software that performs operations on the cartridge

8.1.1. R&D GUI

8.1.2. aQbox

8.1.3. Factory Test

8.1.3.1. Manufacturing Support SW

8.1.4. VolTRAX

8.1.5. Limited Developer

8.1.6. Full Developer

8.2. Super Software Architecture

8.2.1. Issue Management

8.2.2. Routineification

8.2.3. Telematry

8.2.4. Licensing

8.2.5. Software Deployment

8.2.6. Other tools and utilites

9. Processes

10. How to track software

11. The BIG Problem