Agile & Operations

by Patrick Debois

1. Attention To Non-Functional Requirements

1.1. *-ities

1.2. importance of design issues

1.2.1. loose coupling

1.2.2. KISS

2. Agile or Lean or Kanban?

3. Overlap monitoring scripts/ unit tests

3.1. scope of "working software"?

3.2. "IT Ops has graphs!" (Perrick Penet)

4. We have the same product owner

4.1. Project= Focus on adding Business Value

4.2. Operations= Focus on not loosing Business value

5. No programming skills

5.1. ops languages != dev languages

6. ITIL <-> Agile

7. Be involded in project phase

7.1. scope of "customer" / "business people"?

7.1.1. SLA as a requirement

7.2. scope of "team"?

7.2.1. e-g Amazon-type approach

8. agile manifesto

8.1. several types of softwares

8.1.1. sold "in a box"

8.1.2. maintained in house (asp, webservices)

8.2. agile operations?

8.2.1. are tools needed?

8.2.1.1. is virtualisation a requirement?

8.2.2. pair system admin?

8.2.3. refactoring servers?

8.2.3.1. changing parameters

8.2.3.2. patterns

9. Should ops be on your project team?

9.1. where is QA team?

10. specificities of IT Operations

10.1. IT Ops need to operate black boxes

10.1.1. proprietary software

10.1.2. appliances

10.2. operations often needs hw investments

10.2.1. depends on accounting/CFO

10.2.1.1. process/accounting oriented approach

10.2.2. importance of buying decision

10.2.2.1. BDUF: risk or need?

10.3. ops = shared

10.3.1. Shared across projects

10.3.2. shared time

10.3.2.1. project driven

10.3.2.2. Interrupt driven

10.4. ops = scale

10.4.1. production != unit tests?

10.5. persistance over time

10.5.1. as long as in production need to be maintained

10.5.1.1. hardware

10.5.1.2. software

11. what about risk?

11.1. should the notion be treated?

11.2. dev has change in functionalities, ops adds change in importance

11.2.1. importance of initial decisions?