|
All content with label architecture.
Related Labels:
year2010, presentation, year2009, presentasjon, glossary, architecture_principle, oslo2012
Page:
5 reasons to hate architects and how to fix them
(ORG: OSWA Norge Wiki)
Also called 5 signs that your architect should be neutered Policies and no feedbackloops Easier to micromanage and make decisions about simple and technologyrelated stuff than the more complex issues. Myths TODO Totto: opplæringskostnad vs frata tech leads ...
Other labels:
presentation
|
Page:
Above all, do no harm
(KM: Software Architecture)
People ethics for the architect Be wary of your influence: When you suggest a solution, it may get accepted without critical consideration. You remove responsibility from those who will actually execute the task, and limit their feeling of responsibility for the choice. Be humble ...
|
Page:
Architectural building blocks
(Cantara)
Building blocks Vi trenger å finner en granularitert abstraksjonsnivå. Vi trenger også å vite hvem er mottaker (hvem som skal bruker det). some possible dimmensions Teknisk Løsning Forretning Vi ønsker ...
|
Page:
Clear and consistent responsibility power all great architectures
(KM: Software Architecture)
Clear and consistent responsibility power all great architectures As all architects learn, architecture is all about balancing tradeoffs, but there is one trade off which should never be broken; namely the clear and consistent responsibility throughout your system or system ...
Other labels:
architecture_principle
|
Page:
Cloud Psychology - hvordan realisere smarte løsninger
(ORG: OSWA Norge Wiki)
Title Cloud Psychology hvordan realisere smarte løsninger Speaker(s) Anders Bjørnestad, Totto, Webstep Date IASA Norway, Onsdag 16. juni 2010. 18:0021:00 Duration Interactive session, 4560 min Denne presentasjonen vil ...
Other labels:
presentasjon, presentation, year2010
|
Page:
Communication channels in a learning organization
(KM: Software Architecture)
Communication channels 1. Incoming experiences to PAB, from Coordinating Project Architect. 2. From coordinating architect Communicate policies and design rules to Project Tech Lead. Detect policy violations and suggestions for change FROM teach leads. Communicate ...
|
Page:
Even self-organizing teams must have an architect!
(ORG: OSWA Norge Wiki)
2009.06.24 Bård Lind Even selforganizing teams must have an architect! ... and ALL teams must have a TechLead The purpose of this talk is to communicate the responsibilities of the different architectural roles and see how this affects the mandate and responsibilities of an agile, selforganizing ...
Other labels:
presentation, year2009
|
Page:
Filling the glass - finding and choosing the right building blocks
(ORG: OSWA Norge Wiki)
Introduce the metaphore of filling a glass first with large stones, then small stones, then sand... etc Break down an example system into building blocks (stones) Sort these building blocks into different sizes Discuss methods of prioritising placement of the stones in the glass ...
Other labels:
presentation
|
Page:
Hvordan utnytte programvarekompleksitet til din fordel
(Cantara)
Vi opplevde for høy feilrate grunnet for høy kompleksitet i en av releasene våre. Dette fikk oss til å ta grep for å redusere kompleksiteten og dermed også feilraten og Time To Market. Lyntalen ...
Other labels:
presentasjon, presentation, year2010
|
Page:
Laws for organizational architects
(ORG: OSWA Norge Wiki)
Intro Title: laws for organizational architects Speaker: Duration: 35 min Open Space session Audience: Chief Architects, Enterprise architects, Solution Architects, Project Leaders and other Senior Architects Short summary A rundown of the key rules that applies ...
Other labels:
presentation
|
|
|
Label: architecture