process by empowering small, dynamic, government-contractor teams. Agile cannot solve all of the DoD’s IT acquisition challenges, but offers a set of principles that can help reduce cycle times and risks professionals with details on how to adopt Agile development practices to improve outcomes in today’s complex acquisition environment. Agile has emerged as the leading industry software development designed to allow dynamic, tailored, and rapidly evolving approaches to support each organization’s IT environment. “You never know less than on the day you begin your new project. Each incremental

exactly what IT leaders must avoid; continuously transforming and modernizing the company’s IT systems makes Fowler’s strangler pattern into an IT strategy rather than just a coding tactic. If you missed deal with the question of whether it is a near enough fit.I don’t mean that standards are bad. Let’s just agree that they might be overrated. A Better Way – Treat IT as an Enterprise Asset (EA): When user-centric way and match the enterprise’s needs precisely. Risk is low, because the team is constantly adjusting.  Option 2: Compare that to the risk of buying a vendor’s product, where the investment is one

Summary [1] Bill is an IT manager at Parts Unlimited. It's Tuesday morning and on his drive into the office, Bill gets a call from the CEO. The company's new IT initiative, code named Phoenix Project, is critical very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill's entire department will be outsourced. With the help of a prospective board member and his mysterious Unplanned work “What can displace planned work? Unplanned work. That’s why Erik called it the most destructive type of work. It’s not really work at all, like the others. The others are what you planned

successful technology transformation but requires substantial changes in behavior at every level, and Mark’s thorough analysis will prove invaluable to leaders who must execute it.” – Jez Humble, CTO, DevOps process. Brining Lean Principles to Software Development: Kanban is David Anderson’s approach to bringing Lean principles into software development while driving fear out of the transformation depends on whether I am satisfied with its plan. I might ask these questions when I review a team’s plans:  What are the business outcomes the team is trying to achieve? What kinds of activities do

Let’s ask a question that has a chance to actually change things: “What is the set of incentives that drives bad behavior?” I truly doubt that any of the Beltway bandits sees themselves as bad people well-meaning. It’s the system that has failed them, and us. But how do we change it? How do we encourage transparency, priori- ties, and accountability? You know the answer: Scrum. Let’s start a few thousand state does is make decisions. We want to find a way to leave less paper on a desk.”1 The governor’s plan has five points that could have been plucked from any campaign platform: 1. A “world-class”

help him break out of conventional ways of thinking to see what needs to be done. The story of Alex's fight to save his plant is more than compulsive reading. It contains a serious message for all managers software? What is inventory? Two phenomena which are found in every plant Story: Alex takes his son’s boy scout troop on a hike. He can’t seems to keep the line together and they are falling way behind ability to slow down. Or stop. What’s happening isn’t an averaging out of the fluctuations in various speeds, but an accumulation of the fluctuations, and mostly it’s an accumulation of slowness because

poor quality 3. Consider when we have an annual schedule for software releases, where an entire year’s worth of code that Development has worked on is released to production deployment. Like in manufacturing possible c. Gary Gruver observes, “It’s impossible for a developer to learn anything when someone yells at them for something they broke six months ago—that’s why we need to provide feedback to everyone decisions.” 2. Greatness is not achieved by leaders making all the right decisions—instead, the leader’s role is to create the conditions sotheir team can discover greatness in their daily work. In other

pre-production, and CD pipeline) iii. Ian Malpass, Etsy – “If Engineering at Etsy has a religion, it’s the Church of Graphs. If it moves, we track it. Sometimes we’ll draw a graph of something that isn’t Remove the silos of information – Developers don’t just log what’s interesting to development. Operations don’t just monitor what’s up or down. ii. Modern Monitoring architecture 1. Data Collection internal issues 5. Fatal – forces a termination iv. Examples of potentially significant events (Gartner’s GTP Security & Risk Management group) 1. Authentication/authorization decisions 2. System and data

on behalf of the business; it is to steward the asset that is the total of all of the enterprise’s IT capabilities—an asset that has functional capabilities (how it is used today) but also latent capabilities is a kind of feedback cycle that lets us make good decisions in the normal course of work.  Let’s say that we are deciding between two different open source products for building a piece of the system due to capacity constraints or to the governance process’s limitations. A picture of today’s emerging workforce. These characteristics of today’s emerging workforce reinforce the changes I have been describing

Post-Mortem – meeting to examine “mistakes in a way that focuses on the situational aspects of a failure’s mechanism and the decision- making process of individuals proximate to the failure.” – John Allspaw and availability b. Don’t inspect security in at the end, it’s integrated as part of our daily work i. Make security part of everyone’s jobii. Integrate preventative controls into our shared repository process vii. Reduce reliance on separation of duties 2. Ch. 22 – Information Security as Everyone’s Job, Every Day a. Many DevOps organizations have better results than when security is organized as