Carnegie Mellon University
FedCLASS_Case Study of Agile and Lean Practices in the Federal Government.pdf (1.26 MB)

FedCLASS: A Case Study of Agile and Lean Practices in the Federal Government

Download (1.26 MB)
This case study tells the story of the development of a critical IT system within an executive department of the U.S. federal government, using iterative, Agile, and Lean development methods and cloud-based technologies. This study reports the successes and challenges of using this new development approach in a government software development environment so that other government entities can benefit from the experiences of this project. The study is based on conversations with team members, observations of team activities, and examination of work products, documentation, and program guidance. The report describes the organizations responsible for creating the software solution, establishing the development process, and structuring acquisition activities. It then details the product development process in chronological order and describes the development approaches and technologies. It also puts events into the context of external environmental influences to present a development effort as it confronts real-world challenges. The final section describes insights gleaned during the research of this case study and includes analysis of the organization’s experiences with Agile and Lean adoption, technical approaches, and project leadership. These insights may benefit future Agile projects in the federal government and the software engineering community as a whole.


Publisher Statement

This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be construed as an official Government position, policy, or decision, unless designated by other documentation.References herein to any specific commercial product, process, or service by trade name, trade mark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute. NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT.



Copyright Statement

Copyright 2018 Carnegie Mellon University. All Rights Reserved.

Usage metrics


    Ref. manager