Kicking @$$ with Kanban and DevOpsJim Tunnessen
schedule 1 year agoSold Out!
In 2014, US Citizenship and Immigration Services Digital Innovation and Development Group, USCIS DID(it), implemented a portfolio level Kanban process to improve efficiency and delivery of operations, maintenance, and enhancements of existing mission critical software applications. This change in the process and culture of the organization resulted in a year over year (FY13 - FY14) 163% increase in deployments, a 145% increase in the number of user stories deployed, and an increase in end-user and developer satisfaction. These annual metrics were all surpassed within the first five months of FY15. This talk will discuss how we were able to accomplish this by adjusting our process, culture, documentation, and organization; and how it led to increasing our effectiveness and processes with proprietary software development.
How to Use Change Metrics to Manage Agile RiskK. Michele Bumbary
schedule 1 year agoSold Out!
Risk management is a fundamental element of program management. This presentation suggests a new idea for agile risk management for agile software development programs.
What is the Issue? The principal problem discussed in this presentation is identifying code changes and growth (risk of increasing feature story points) in agile development, and how to predict and adjust feature scope to maintain velocity (manage software change).
The constant incorporation of change and deliveries with agile development may influence programmatic schedule and scope risk differently from other methodologies (i.e. Waterfall, Spiral, etc.) where the release cycles maybe longer in duration and change is less frequent.
What is the Definition of Risk? Let us keep it simple and rely on the ISO standards for risk: Risk is the effect of uncertainty on objectives. It can be expressed in terms of a combination of the consequences of an event (including changes in circumstances) and the associated likelihood of occurrence.
What is the Point? This presentation is based on the presenter's first-year experiences of a current and real-world application of enterprise Agile Development. This is an opportunity to share with the agile community, possible change metrics that may be used to monitor and control risk.
The point is straight-forward,
- What level of change tracking provides accurate risk assessment in an agile/lean environment?
- What change should be tracked?
- How can story point changes in features be extracted from Earned Value Data?
Let us look at the characteristics of the real world program case study:
- Industry: Government Contractor
- Size of Program: Medium
- # of Release Trains: One(1) Release Train
- # of Scrum Teams: Five (5) Scrum Teams
- # of Releases: 9
- # of People: ~ 100
- # of Months: ~ 24
- Agile Methodology: SAFe™ Agile
- Business Methodology: Earned Value Management (EVM) is required.
- Presenter's Role: Program Manager