Virtualization
Software Development
Requirements Analysis
Business Process
Re-engineering and Knowledge Management
Systems Integration/Engineering
Independent Verification and Validation
Training Development and Delivery
Program/Project Management

CORE BUSINESS

Software Development

At Knowledge Link, we build software for clients in the Intelligence Community to solve their complex problems and serve their changing needs. Rarely are traditional software development processes suited to this work. Instead, Knowledge Link uses new “Agile” techniques for software development to iteratively develop software quickly and successfully.

Agile software development strives to break down software development into small pieces which can be accomplished quickly.   As each piece of the software is completed, it is evaluated.  If any piece is found wanting, it is sent back for more work.   When all the pieces are done, the software is done – successfully.

Scrum is one of the new Agile software development methods that Knowledge Link recommends. 

Many Knowledge Link personnel are ScrumMaster-Certified Developers.  We recommend the Scrum software development methodology for dealing with complex problems and changing needs.  In these situations, Scrum results in significant time and cost savings whether developing software from scratch or modifying existing COTS/GOTS programs for a client.

What Is ‘Scrum’?

The term “Scrum” comes from the game of Rugby, where it refers to a small team of players huddled together to try to push the ball down the field.  

At the beginning of the Scrum process, there is an initial planning phase to define the vision of the project and to identify a number of initial pieces of work that need to be done. 

Small teams are assigned to perform each of these pieces of work.  Each team will “Sprint” to complete its piece as quickly as possible and turn it over to the client and stakeholders for feedback. 

As the Sprints are completed and the work delivered is evaluated, the plans are updated, new Sprints (pieces of work) are identified and the Scrum project moves forward.