1. Applications to web-development
1.1. Breakdowns
1.1.1. Page view
1.1.2. Components view
1.1.3. Lines of code
1.1.4. Function points
1.1.5. Use cases
1.2. Other factors
1.2.1. Vacation
1.2.2. Holidays
1.2.3. Maintenance
1.2.4. Migration
1.2.5. 6 vs 8 hours
1.2.6. Historical estimates
1.2.6.1. Reestimation
1.2.7. Effort multipliers
1.2.7.1. Cocomo II
1.2.8. Reuse
1.2.9. Trainings
1.2.10. Deployment
1.2.11. Architecture
1.3. Typical architecture
1.3.1. Environment configuration
1.3.2. Backend
1.3.3. Frontend
1.3.3.1. Design
1.3.3.2. Slicing
1.3.4. Infrastructure and monitoring
1.3.5. Quality attributes
1.3.6. Documentation
1.3.7. Tests
1.3.8. Migration
1.3.9. Integration
2. Assumptions
2.1. Functional
2.2. Staffing
2.3. Priority
2.4. Input
2.5. Contigency
2.6. Process
2.6.1. Project management include or not
2.6.2. 20% - 30% meeting overhead
2.7. Quality
2.7.1. Refactoring
2.7.2. Percentage to bug fixing
2.8. Skills
2.9. Constraints vs assumptions
3. Advices and issues
3.1. Plan rollout initally
3.2. Ask about budget
3.3. Scope creep
3.4. Too many assumptions
3.5. Expect changes
3.6. Don't overestimate (consider EPAM's reality)
3.6.1. Shadow resources
3.6.2. Non production activities
3.6.3. Too optimistic/pessimistic estimates