Lesson 4 Flashcards
Quality triangle components / project review
Scope
Cost
Time / Schedule
Two schools of IT Project Management
- Traditional (Waterfall) PM
2. Agile PM
Steps of Waterfall PM
- Requirements
- Design
- Implementation
- Verification
- Maintenance
Steps of Agile PM
- Requirements
- Design
- Develop
- Test
- Deploy
Main difference between Agile PM and Waterfall PM
The scope.
Waterfall: scope must be established before software development.
Agile: scope is not clear it can change during the project.
Waterfall: Constantly changing requirements/scope due to?
- Lack of discipline
- Not enough planning
- Failure to establish clear requirements
- Allowing scope creep (success is a moving target)
Agile: Constantly changing requirements/scope because of?
- Requirements do not exist. Users do not know what they want from an application at the beginning of the project.
- Users cannot communicate their needs at the beginning of the project.
Waterfall: Constantly changing requirements/scope solutions.
Discipline in planning
Agreement in advance on what the project will accomplish (what users’ requirements are)
Requirement outside the scope is only accepted if an official notice is given that adjusts the budget and schedule of the project
Create contingency plans for possible problems (risks)
Agile: Constantly changing requirements/scope solutions.
Don’t waste time on too much planning
Start building the system fast
- Create prototypes for small projects
Detailed walkthroughs of a process for big projects
Accept that you will inevitably have messes.
- Better early mess than a late-breaking disaster.
Fail faster to succeed sooner
Active attention to the detail
Agile PM components / best fits / advantages
High exploration-factor
High customer responsiveness
Organizations with innovative cultures
Waterfall PM components / best fits / advantages
Clear requirements at the beginning
Small or no changes to requirements during the project
Patient customers
Mechanistic culture
Two (traditional) approaches for keeping things on schedule (planning)
Gantt chart
Critical path
IT Project Management Maturity (traditional) approach.
Name the five maturity levels/scores
CMMI: Capability Maturity Model Integration
- Initial
- Managed
- Defined
- Quantitatively managed
- Optimizing
IT architecture definition:
The overall design of computing systems
Three applications/systems of IT architecture (give some examples)
Back-end systems
- Accounting
- Human resource
- Finance
- Production
Middle-end systems
- Order fulfillment
- Inventory management
- Shipping
Front-end systems
- Order placement
- Customer relationship management (CRM)
Define spaghetti systems
Spaghetti systems are the results of kludges for fast system development
Kludge: a quick-and-dirty solution that is clumsy, inelegant, inefficient, difficult to extend, and hard to maintain.
IT risks and its corresponding Business risks due to spaghetti systems
Complexity of system interdependencies
–> Service outage
Difficult to integrate systems
- -> Inadequate (financial) controls
- -> Decision making based on incomplete data
- -> Vulnerability to internal security threats
Difficult to implement real-time systems
–> No support for real-time response to market
Solution for spaghetti systems
Enterprise Architecture (EA)
Requirements/steps for Enterprise Architecture (EA)
- Focus on whole organization
- Develop blueprints of current architecture
- Develop blueprints of desired architecture
- Develop roadmap for transition
Enterprise Architecture (EA) + Agile PM
Agile EA
Enterprise Architecture (EA) is more aligned with?
Traditional (Waterfall) PM
De-escalation
The termination or redirection of an escalating IT project
De-escalation process (4 phases)
Phase 1: Problem recognition
Phase 2: Re-examine prior course of action
Phase 3: Search for alternative action
Phase 4: Implement exit strategy
7 key roles in de-escalation process
Messenger Exit sponsor Exit champion Exit catalyst Exit blocker Legitimizer Scapegoat
6 bases of power (for compliance)
Reward power (personal/impersonal) –> give rewards
Coercive power (personal/impersonal) –> force by threat or punishment
Expert power –> expertise
Informational power –> convincing
Legitimate power –> demand through right
Referent power –> celebrities
Legitimate power subcategories
Position (authority)
Reciprocity (you’re indebted)
Equity (compensate)
Dependence (responsibility for someone in need)
Roles phase 1 of de-escalation process
Phase 1: Problem recognition
Messenger (only in phase 1) Exit sponsor Exit champion Exit catalyst Exit blocker Legitimizer
Roles phase 2 of de-escalation process
Phase 2: Re-examination of prior course of action
Exit sponsor Exit champion Exit catalyst Exit blocker Legitimizer
Roles phase 3 of de-escalation process
Phase 3: Search for alternative action
Exit sponsor
Exit champion
Exit catalyst
Exit blocker
Roles phase 4 of de-escalation process
Phase 4: Implement exit strategy
Exit champion
Exit blocker
Legitimizer
Scapegoat (only in phase 4)
