16 Lecture Flashcards

1
Q

What’s special about global projects?

A
  • Distance
  • Time Zones
  • Culture
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Which communication patterns are there?

A
  • Planned vs unplanned
  • Synchronous vs asynchronous
  • Vertical vs horizontal
  • Formal vs informal
  • Internal vs external
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the agile cornerstones?

A
  1. Enable People (visualize of teams , resp)
  2. Close collaboration (Demos where teams share)
  3. Team autonomy (Autonomy in teams)
  4. Continous improvement (Continous improvement epics)
  5. Innovation (time for innovation between sprints)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the difference between Projects and Products

A

Product development is done with long term organization and with no decided end date.
Projects is optimized for short term delivery.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the Backbone of User Story Mapping

A

essential activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the Walking Skeleton of User Story Mapping

A

the least number of necessary tasks to support

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is a Software Architecture

A

The sum of decisions that are hard to change

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Name three advantages of Software Architecture

A

+ Turns big problems into smaller more manageable problems
+ provides a vocabulary for talking about complex ideas
+ helps avoid costly mistakes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the duties of a Software Architect

A
  • Clarify Requirements
  • Design Structures
  • Design (Crosscutting) Conceps
  • Communicate Architecture
  • Shepard Implementation
  • Evaluate Architecture
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are the 6 Principles of Continuous Architecture

A
  1. Architect Products not just solutions for projects
  2. Focus on quality attributes
  3. Delay Design decisions until they are absolutely necessary
  4. Architect for change
  5. Architect for build, test, and deploy
  6. Model the organization after the design of the system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Ways to deal with large systems

A
  1. Chunking -> Modularity
  2. Hierarchies -> Hierarchical Layering
  3. Schemata -> Pattern Consistency
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

The more teams, the more …

A

coordination is necessary -> Software Architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are architectural decisions?

A
  • Spanning several subsystems or components
  • Involving compromises and tradeoffs
  • Involving intense stakeholder discussions
  • Founded in organizational or political constraints
How well did you know this?
1
Not at all
2
3
4
5
Perfectly