Lec 4

Question 1

Traditional v Agile

Answer 1

Traditional : constantly chAnging requirements because lack of discipline, failure to establish clear requirements

Model:
Requirements > design > implementation > verification > maintenance

Agile: constantly changing requirements because requirements do not exist, users can’t communicate needs at begging of project, problems cannot be anticipated as business environment changes

Model:
Requirements> design>develop > test and repeat

Question 2

Traditional v agile/ suggested solutions

Answer 2

Traditional suggested solutions:
Disciple in planning
Firm agreement in advance
Req outside scope only given if permitted 
Contingency plan created

Agile suggested solutions:
Not much planning
Build system fast
Accept errors
Fail faster quicker succeeding
Active attention to detail

Question 3

Choosing traditional or agile

Answer 3

Traditional:
Clear req at beginning
Small or no changes during project 
Patient customers
Mechanistic culture

Agile:
Hugh explanation factor projects
High customer responsiveness
Organisations with innovative cultures

Question 4

How to keep projects on schedule

Answer 4

How to keep projects on schedule:
Find all tasks to be performed and their interdependencies

Find the critical path (path where if delays add scrutiny to delays to overcome)

Question 5

3 IT Infrastructure

Answer 5

It infrastructure:
1.back end systems > accounting hr

2. Middle end systems > shipping
3. Front end systems > customer relations management, order placement

Question 6

IT Infrastructure issues: spaghetti systems

Answer 6

Issue with it infrastructure is spaghetti systems. This is the result of kludge for fast system development.

A kludge = a quick and soft solution that is inefficient, dirty, clumsy and hard to maintain

Question 7

Risks of poor IT Infrastructure issues

Answer 7

Risks of poor it infrastructure issues;

Kludges- service outrage

Insufficient integration between systems

Lack of real time functionality

Question 8

Factors for selecting a vendor

Answer 8

Factors for selecting a vendor:

Fit between company’s tech platform and vendors solution
Prev history of vendor
Skill level of team that vendor assigns

Question 9

Phases of de escalation process:

Answer 9

Phases of deesclation process:

Phase 1: problem recognition

2: reexam of prior course of action
3. Search for alternatives
4. Exit strategy

Question 10

Key roles in de escalation process

Answer 10

Key roles in deescalation process:

Messenger - gives problem description
Exit sponsor - authority to push exit
Exit champion - actively pursue deescaltion
Exit catalyst - show probs of existing
Exit blocker - slows exit down 
Legitimiser - external assessment 
Scapegoat - to blame for project failing

Question 11

Bases of power (compliance)

Answer 11

Bases of power complaince:

Reward power - give rewards for compliance
Coercive power - force through threat
Expert power - compliance based on expertise
Informational power - compliance through intelligence
Legitimate power - compliance through position
Referent power - Induce behaviour based on influencing agent