Competencies: Professional > Project Management
Project Management
Body of Knowledge
| Topic | Description | Relevance | Career Tracks |
|---|---|---|---|
Change Control |
Structured process for requesting, reviewing, approving, and implementing changes to production systems. Includes pre/post verification, rollback planning, approval workflows, and documentation requirements. |
Critical |
IT Manager, Change Manager, Infrastructure Engineer |
RCA Methodology |
Root Cause Analysis techniques for identifying the underlying causes of incidents and failures. Encompasses 5 Whys analysis, prevention extraction, pattern identification, and continuous improvement processes. |
High |
Incident Manager, Problem Manager, Senior Engineer |
Agile Methodologies |
Scrum, Kanban, sprint planning, retrospectives, agile ceremonies |
High |
All Engineering |
Estimation |
Story points, t-shirt sizing, planning poker, estimation accuracy |
High |
All Engineering |
Task Breakdown |
Work decomposition, user stories, acceptance criteria, definition of done |
High |
All Engineering |
Risk Management |
Risk identification, mitigation strategies, contingency planning |
High |
Project Manager, Senior Engineer |
Stakeholder Management |
Expectation setting, progress reporting, scope management |
High |
Project Manager, Tech Lead |
Technical Planning |
Technical specifications, design documents, implementation plans |
High |
Senior Engineer, Architect |
Prioritization |
MoSCoW method, RICE scoring, impact/effort matrices, backlog grooming |
High |
Product Manager, Tech Lead |
Documentation Standards |
Process documentation, runbooks, knowledge management |
High |
All Engineering |
Personal Status
| Topic | Level | Evidence | Active Projects | Gaps |
|---|---|---|---|---|
Change Control |
Advanced |
STD-005 change control standard — pre/post verification, rollback plans, approval workflows; applied to ISE policy changes and network cutovers at CHLA |
No ServiceNow/Jira change management integration |
|
RCA Methodology |
Advanced |
STD-010 RCA standard with 5 Whys, prevention extraction, pattern identification; 10+ documented RCAs across ISE, DNS, certificate, and build failures |
No formal ITIL problem management process |