Agile Development

Is it Agile time yet? Um, yes.

We happily use Agile for all our development! Feds tailor the process and we execute the plan. Sometimes it’s Scrum, sometimes Lean or Kanban. Our big-time programs blend ’em for best results. Regardless, we maximize velocity and deliver flawlessly. The result: Useful software. Business value.

On time and on budget. ; )

AGILE PRINCIPLES

When we sign-up for a project, we do a bunch of things. Ikr? We also pledge to…

Deliver useful software regularly
Accommodate changing requirements
Measure progress through working software
Cooperate daily with clients

Prefer face-to-face communication
Apply sound, practical designs
Devise simple architectures and codebases
Promote self-organizing teams

Btw, our experience = your success. As a federal prime, our Agile resume includes:

● 15 Years of task order execution

● Dozens of mission-critical systems

● 100+ system deployments

● Hundreds of sprints

● Thousands of backlog items

● Tens of thousands of federal client users

● Millions of general public users

● Billions of productions transactions

Lean practices

Efficiency and practicality through Lean

Lean Practices

1. Eliminate Waste
2. Build Quality In
3. Create Knowledge
4. Defer Commitment
5. Deliver Fast
6. Respect People
7. Optimize The Whole

Agile Manifesto

Inspiration from the Agile Manifesto

Satisfy the customer with early and continuous delivery of valuable software
Welcome changing requirements, even in late development
Deliver working software frequently (weeks rather than months)
Business people and developers must work together daily throughout the project
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done
Face-to-face conversation is the best form of communication (co-location)
Working software is the principal measure of progress
Promote sustainable development, able to maintain a constant pace
Pay continuous attention to technical excellence and good design
Simplicity—the art of maximizing the amount of work not done—is essential
Best architectures, requirements, and designs emerge from self-organizing teams
Regularly, the team reflects on how to become more effective, and adjusts accordingly

Scrum Elements

Flexibility and quality using Scrum

The Scrum Team

The Product Owner
The Development Team
The Scrum Master

Scrum Events

The Sprint
Sprint Planning Daily Scrum
Sprint Review
Sprint Retrospective

Scrum Artifacts

Product Backlog
Sprint Backlog
Increment

Kanban Principles

Change and improvement with Kanban

Start with what you do now
Agree to pursue incremental, evolutionary change
Respect the current process, roles, responsibilities & titles
Encourage acts of leadership at all levels

Download a complete, printable version of this capability!