Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

Agile & Operations by Mind Map: Agile & Operations
0.0 stars - 0 reviews range from 0 to 5

Agile & Operations

Attention To Non-Functional Requirements

*-ities

importance of design issues

loose coupling

KISS

Agile or Lean or Kanban?

Overlap monitoring scripts/ unit tests

scope of "working software"?

"IT Ops has graphs!" (Perrick Penet)

We have the same product owner

Project= Focus on adding Business Value

Operations= Focus on not loosing Business value

No programming skills

ops languages != dev languages

ITIL <-> Agile

Be involded in project phase

scope of "customer" / "business people"?

SLA as a requirement

scope of "team"?

e-g Amazon-type approach

agile manifesto

several types of softwares

sold "in a box"

maintained in house (asp, webservices)

agile operations?

are tools needed?, is virtualisation a requirement?

pair system admin?

refactoring servers?, changing parameters, patterns

Should ops be on your project team?

where is QA team?

specificities of IT Operations

IT Ops need to operate black boxes

proprietary software

appliances

operations often needs hw investments

depends on accounting/CFO, process/accounting oriented approach

importance of buying decision, BDUF: risk or need?

ops = shared

Shared across projects

shared time, project driven, Interrupt driven

ops = scale

production != unit tests?

persistance over time

as long as in production need to be maintained, hardware, software

what about risk?

should the notion be treated?

dev has change in functionalities, ops adds change in importance

importance of initial decisions?