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)