Implementing Agile to Support the Delivery of Productivity Software in the Federal Governemnt
We all know that agile development will increase the likelihood of a good outcome for software development projects. This talk is a case study describing how a federal government agency partnered with a software vendor to rescue a failing software development project. The project was an initiative of the head of the agency. The scope of the project was to enhance the custom software productivity application that has over 2000 users and supports the agency's primary mission. The following agile practices were implemented which benefited the project.
Daily stand up meetings
This was all done on government contract for a firm fixed price. This session will describe how and why these processes were implemented and how they benefited to project and its stakeholders.
Outline/Structure of the Talk
- Problem statement
- Identification of agile practices
- Discussion of implementation
- Lessons learned
The desired outcome is for other practitioners in this space to consider what is possible and how to improve outcomes by implementing agile best practices.
Government technology managers and practitioners, Government contractor managers and practitioners
schedule Submitted 6 years ago
People who liked this proposal, also liked:
Yuval Yeret - Flow - A Way Towards DevOps Culture in the Legacy EnterpriseYuval YeretEnterprise Agile Coach and CTOAgileSparks
schedule 6 years agoSold Out!
DevOps is a very popular buzzword. Many people associate it with tools like Chef, Puppet, Continuous Deployment etc. But DevOps is really a higher form of agility. It is a blueprint for a great culture and and process between the different groups involved in the delivery pipeline. The big question is how to achieve it. If you are founding a startup today, it can be quite easy to take that blueprint and use it to create your process, hire the right versatile flexible people, and start delivering without any technical/automation debt or friction. But most of us are not founding new startups. Most of us already have a running operation with people, culture, process that matured over the years and despite its flaws is currently the way we do things. Changing that is non-trivial.
For things to change people need to understand WHY change, what we are changing, and we need an effective process for managing the change itself (HOW to change). So what ARE we changing to? DevOps is highly focused on looking at the whole value stream from idea to value and ensuring effective flow through this pipeline.
Kanban is ONE way of HOW to change towards an end to end flow. It starts by visualizing all the work flowing in the pipeline, then managing the flow focusing on finishing things end to end rather than starting in order to stay busy. It continues to what we call the “Work in process Diet” – Straining the flow more and more in order to identify obstacles to tighter and tighter DevOps culture/operation and faster feedback cycles. You can expect to come out of this session with ideas how to take your current operation and DevOpsify it in a safe evolutionary way using the Kanban method as well as an understanding WHY DevOps tools are required as part of this journey.
Paul Boos / Laura M. Powers - Understanding How Collaboration Improves ProductivityPaul BoosIT Executive CoachExcellaLaura M. PowersVice President & Product OwnerAgile Learning Labs
schedule 6 years agoSold Out!
We've all heard how we need to collaborate better, but what does this really mean? What results can I expect to see with better collaboration?
This workshop will demonstrate how productivity increases with greater collaboration and how to create better a more collaborative environment. In the session you will not only have an opportunity to experience this relationship with a relatively simple learning game, but we'll look behind the curtain at the science and how some various behavioral models explain why this relationship exists. We'll then explore some tactics you can use to help teams collaborate better and close with an exploration of what either helps or hinders collaboration and how you can use this information as well as the game with your teams.
If you have an interest in improving productivity of your team or the teams you serve, then this is the session for you.