Prozess Innovation - notes

ein paar notes zu prozess innovationen....

Standard
- Schlanke und wiederholbare Prozesse
- Prozesse müssen sich internen Bedürfnissen anpassen

Effizänz durch wiederholte Anwendungen
- Mit Wiederholungen steigert sich die Effizienz
- Lernkurve ist sichtbar: Skepsis, Euphorie, Frustration, Beherschung

Payback Effekt



- Breakeven wird schneller erreicht mit effizienten Leistungssteigerungen

Sicherheit / weniger Risiko

- Standardtisiertes vorgehen
- Verlässliche Angaben - Machbarkeit / Kosten / Projektdauer
- Beherschte Prozesse reduzieren das Risiko einzelner Mitarbeiter

Transparanz
- Probleme können frühzeitig erkannt werden
- Vorgesetze können durch Transparenz schnellere Entscheide fällen
- Es kann mehr Eigenverantwortung übernommen werden

Mitarbeiterzufriedenheit
- Industriestandards motivieren Mitarbeiter
- Steigert die Bereitschaft für Veränderungen
- Ausbau der persöhnlichen Fahigkeiten
- Plan - und Steuerbare Mitarbeiterentwicklung
- Bessere Zusammenarbeit im Team
- Steigerung des Marktwertes von Mitarbeitern

Benchmarking
- Priorisierung von Massnahmen

Projekt-Masterplan (Iterationsvorgehen)


Coaching
- Tell me and I forget, teach me and I remember, involve me and I learn (Benjamin Frenkel)

Performance
- Eingespielte Verhaltensweisen bringen Sicherheit und Erfolg

Erfolg = Wissen x Verhalten²

- Nur wenn Mitarbeiter verstehen, und Prozesse vorgelebt werden nehmen Sie den Lernaufwand auf sich

Performance II

Mitarbeiter:

• Sichere Arbeitsplätze
• Persöhnliche Weiterbildung
• Erreichen von Zielvorgaben
• Interessante Tätigkeiten
• Teamkultur
• Annerkennung
• Eigener Marktwert
• Moderne Infrastruktur

Akzeptanz Stärken (Transparenz)

• Frühzeitige und glaubwürdige Informationen von Veränderungen
• Berücksichtung der Mitarbeiterbedürfnisse und Erwartungen
• Kommunikation / Feedback
• Einbezug von Mitarbeitern
• Erfahrungsaustausch
• Meilensteine Feiern!!!!

Templates

• jeder Mitarbeiter muss Informationen in 5 min finden

Metriken

Prozess

• Periodische geprüfte und auswärtungstand
• Projektreifegrad

Produkt

• Anzahl Defekte (pro Woche)
• Anzahl Use Cases
• Anzahl der Change Requests
• Anzahl der Templates
• Anzahl der Versionen

Justin Etheredge: How To Guarantee That Your Software Will Suck

Justin Etheredge wrote an article: How To Guarantee That Your Software Will Suck

here is an overview:

1) Don't give your developers the tools they need to do their jobs.
2) Just jump right in, plans are for chumps.
3) Set strict deadlines on projects that will take "tens of thousands of man hours".
4) Spend hundreds of hours writing ridiculously detailed documentation.
5) Refuse to buy them more than one monitor.
6) Buy cheap hardware.
7) Keep asking them to multi-task.
8) Write everything yourself.
9) Expect your developers to sit quietly in front of their computer 8 hours a day.
10) Purchase tools without consulting those who will have to use them.

some of the points i absolutely agree with :-)

Project phases

Preparation phase

Understand problems even if you need to request additional meetings for this. there is always somebody who can explain you details. creation of a basic to make decisions (Date, Budget, Environment, etc.). it will help all team members if you have a small model with a term overview - so everybody talks about the same. Try to identify risks and create a ranking of them - I use usually a range of 1 - 5. Each risk will be rated and it makes sense to discuss them with other people in your team.

Design phase

create all available use cases for your application. explain different use cases with 2 / 3 simple sentences. at this stage you start with architectural questions for system and environments. i suggest you start with a small front-end prototype which you can present your end users. you gone receive tons of feedback's.

Creation phase

start up with your development were you firstly describe your use cases deep enough that you able to develop unit tests and think about using aspect programming.

Entry phase

create presentations for the software - best case is if customers / target clients already know about what you are gone talk then we have integrated them deep enough into previous phases. The entry phases are usually very stressful and harm business incoming therefore don't forget: as better you prepare yourself as easier it gone be!

Important principles of agile projects

spunk

trust to solve problems tomorrow once they appear tomorrow. Feel free to come up with your concerns about actual problems today on a constructive way - do it before somebody else does it.

communication

arrange face2face meetings - project members which meet they feel more comfortable to work together. Any problem is important to solve - communication problems are most important to solve.

feedback

force acceptance tests of your target clients, make reviews with other team members to receive feedback's about possible better solutions.

simple

search for the simplest solution to solve your problem - exactly to solve upcoming problem. For 5 different problems think about 5 simple solutions instead one very complex solution. next time you know enough about the problem to solve all them together in one very simple solution.