1
Q
Traditional (Waterfall) project management
A
- Product requirements
- Design (Software)
- Implement (Software)
- Verificate functionality
- Maintenance
2
Q
Agile project management
A
Deliver after every step/circle.
3
Q
Changing requirements Traditional method because of:
A
- Lack of discipline
- Not enough planning
- Failure to establish clear requirements
- Scope creep
- Success is a moving target
4
Q
Changing requirements Agile method because of:
A
- No requirements
- Users cannot communicate their needs
- Problems cannot be anticipated -> Business environment is changing.
5
Q
Solutions for Traditional method
A
- Discipline in planning
- Firm agreement in advance
- Requirements outside the scope is only accepted after official notice is given that adjust budget and schedule of the project.
- Create contingency plans for possible risks.
6
Q
Solutions for Agile method
A
- Don’t waste money on planning
- Start building
- Accept that you will inevitably have messes.
- Fail faster to succeed sooner
- Active attention to the detail
7
Q
Choose for Agile method if:
A
- High exploration factor project.
- High customer responsiveness.
- Organization with innovative culture.
8
Q
Choose for traditional method if:
A
- Clear requirements
- Small or no changes to requirements
- Patient customers
- Mechanistic culture
9
Q
Methods used in project management:
A
- GANTT chart
- IT Project planning management maturity
10
Q
IT project planning management maturity
A
5 phases:
- Initial
- Managed
- Defined
- Qualitative
- Optimizing
11
Q
De-escalation process
A
- Problem recognition
- Re-examination of prior course of action
- Search for alternative courses of action
- Implementing an exit strategy
12
Q
Roles in de-escalation process
A
- Messenger
- Exit sponsor
- Exit champion
- Exit blocker
- Legitimizer
- Scapegoat
13
Q
Bases of power within companies
A
- Reward power
- Coercive power
- Expert power
- Informational power
- Legitimate power
- Referent power
