Making change happen
Plan, deliver, and communicate security improvements that actually stick.
Acceptance criteria
Define observable conditions for a deliverable to be accepted.
Agile delivery
Use short feedback cycles to adapt toward a useful outcome.
Backlogs and prioritization
Order work by value, risk, dependencies, and learning needs.
Budgeting and resources
Plan the full cost and capacity needed to deliver and sustain the change.
Change control
Evaluate a proposed change before it alters scope or a running service.
CI/CD pipeline security
CI/CD security protects the systems that transform source into deployed software.
Critical path
Find the dependency chain that constrains a planned completion date.
Decision logs
Preserve the reason for a choice so future work can build on it.
Definition of Done
A shared quality threshold makes completion transparent.
GitHub Actions security
GitHub Actions security depends on workflow triggers, token permissions, runner boundaries, and the trustworthiness of executed code.
Kanban
Make work visible and manage flow rather than only starting more tasks.
Lessons learned
Turn experience into a specific improvement with an owner.
Monitoring delivery and outcomes
Use evidence to understand progress, blockers, and whether the change is working.
PRINCE2 concepts
Use structured governance while tailoring the approach to the project.
Project charters
Establish why the project exists and who can direct it.
Project closure and handover
Confirm acceptance and transfer the work needed to sustain the outcome.
Project dependencies
Identify what must be available before another piece of work can succeed.
Project documentation
Create records that help people decide, operate, and maintain the result.
Project governance
Define authority, decisions, escalation, and accountability for a change.
Project lifecycles
Move a defined improvement from purpose through delivery and review.
Project planning
Connect the intended outcome to work, resources, dependencies, and evidence.
Project risk management
Manage uncertainty that can affect the project’s objectives.
RAID logs
Separate risks, assumptions, issues, and dependencies to support action.
Scheduling and milestones
Sequence work with dependencies and clear decision points.
Scrum
A lightweight framework for delivering value through inspection and adaptation.
Scrum events
Give planning, coordination, review, and improvement distinct purposes.
Secure code review
Secure code review examines implementation details in light of security requirements and plausible misuse.
Software bills of materials (SBOMs)
An SBOM records software components in a machine-readable inventory associated with a product or release.
Stakeholders and communication
Give the right people information and involvement for the decisions they own.
Vulnerable dependency remediation
Dependency remediation evaluates and addresses vulnerable third-party components in a specific application.
Waterfall delivery
Plan sequential stages when requirements and dependencies justify them.
Work breakdown structures
Break the outcome into manageable deliverables without losing the whole.