AGILE DEVELOPMENT

Agile Development

Obsidian provides a comprehensive solution to the government for agile software development, continuous integration, continuous testing and continuous delivery.

Obsidian’s Agile Development Methodology

As a trusted partner to federal agencies and mission operators, we help you anticipate threats, respond rapidly, and build resilient, secure systems that withstand today’s challenges—and tomorrow’s risks.

Lean Thinking

Solutions tailored for federal and critical infrastructure environments.

Continuous Improvement

Cleared professionals with deep expertise in cyber defense and secure systems.

Transparency

Delivering measurable security outcomes that reduce risk and strengthen resilience.

SAFe (Scaled Agile Framework)

Supporting agencies and enterprises with integrity, agility, and dedication.

Agile Methods & Frameworks

Kanban

This development and delivery model works as a fan-in and fan-out process where the development team pull user stories from an intake board and funnels them through staged development until complete

Scrum

This development and delivery cadence focuses on a sprint and meeting structure that includes planning (priorities identified), commitment (decision on the work that is accomplished in a sprint), and communication (through daily standups for commitment status, challenges, strategies).

DaD (Disciplined Agile Delivery)

This framework enables the SCRUM team ‘sprint zero’ to take flight, commonly utilized for base platform technology and architecture tradeoffs, as well as programming language, build tools, and test decision making.

LeSS (Large Scale Scrum)

This development within a SCRUM team-of-teams framework enables large-scale planning, typically involving a SCRUM comprised of the SCRUM team leads at or near the end of the SCRUM team sprints.

Agile Delivery Practices

Frequent Delivery

Projects deliver usable products to users at frequent sprint intervals to meet mission needs

Time-boxed Iterations

We have fixed-length, 2-week iterations as a standard cadence for planning, completing, and demonstrating functionality

User Stories

These are our basic unit of planning, executing, and tracking work, with user stories being defined as small, independent, and testable units of functionality

Product Owner

Each project has a representative for the business integrated with the team with the authority to make timely decisions for development, prioritization, and acceptance

Release Planning

We conduct release planning exercises that culminate in release planning reviews (RPRs)

Iteration Reviews

We facilitate reviews at the end of each iteration to demonstrate and test functionality to solicit feedback from stakeholders

Retrospectives

We hold meetings at the end of each iteration to reflect on our team’s performance and identify opportunities for improvement

Continuous Testing

We use automated tools to test user stories against acceptance criteria in various test environments during the iteration the stories are developed