Software process of change

Meer zoals dit

What's Out There? Resources to support the work of K-12 Classroom Educators in Ontario (OERB, vLe, OSAPAC, Edugains/Edusource) August 2015

door Joe Russo

Navis Solutions and Services Mind Map

door Mario Zapata

CM - Chapter 3 - Why organizations change

door Sander van der Kolk

UTSC Department of Management

door Stephanie Perpick

Software process of change

Where we want to go

Tooling

Porcesses

Planning

Testing

Development

Code

Modularization

Design patterns

Software Pattern

Architecture

Vendor locking

Message Driven

Hexagonal

How should we get there

Keep it in motion

Visibility

Working with management

Biggest road blocks

Fear

We afraid of new stuff

Cost

Software flexibility/rigidity

Outbreaks limitation

Money cost of not implementing

Money cost to implement

Why should we go there

Consequences of keeping current approach

Possible drawbacks

Benefits of change

Convincing managment

People

Cultural differences

I takes affort to learn new ways

Resistant to new approach

Comfort in current state

Keep it running

Started process should be finished

Changes take time

App should work all the time

Where are we

Technology

Identify pains

Software culture(unspoken rules)

Software related process