The Phoenix Projectoutsourced. With the help of a prospective board member and his mysterious philosophy of The Three Ways, Bill starts to see that IT work has more in common with manufacturing plant work than he ever communications, and effectively serve the other business functions at Parts Unlimited. Key Concepts The Three Ways [2] The First Way emphasizes the performance of the entire system, as opposed to the performance com/Phoenix-Project-DevOps-Helping-Business/dp/0988262509/[2] The Three Ways: The Principles Underpinning DevOps, Gene Kim, http://itrevolution.com/the-three-ways- principles-underpinning-devops/0 码力 | 3 页 | 154.45 KB | 5 月前3
A Seat at the Table - IT Leadership in the Age of Agilityuncertainty, your choices will often turn out to be wrong.Agile and plan-driven models have very different ways of dealing with uncertainty. Plan driven approaches, even Waterfall, have always acknowledged that in this sense is simply an efficient process we use to select among alternatives. Shadow IT Agile ways of working support a community approach to IT, where IT leaders achieve their objectives by mobilizing employee happiness, and innovation. Manager of Uncertainty: Agile and Lean thinking give IT powerful ways to manage uncertainty. By establishing short, robust feedback cycles and flexible decision-making0 码力 | 7 页 | 387.48 KB | 5 月前3
The DevOps Handbookrestore service (168 times faster) 4. An Introduction to The DevOps Handbook xxi 5. PART I—THE THREE WAYS 1 a. Introduction i. THE LEAN MOVEMENT 1. manufacturing lead time required to convert raw materials predictors of short lead times was small batch sizes of work b. Agile, Continuous Delivery, and the Three Ways 7 c. The First Way: The Principles of Flow 15 i. MAKE OUR WORK VISIBLE 1. A significant difference observe the importance of organizational culture on safety and performance. Dr. Westrum defined three types of culture: a. Pathological organizations are characterized by large amounts of fear and threat0 码力 | 8 页 | 22.57 KB | 5 月前3
A Seat at the Table: IT Leadership in the Age of Agility - Part 2development have changed: Changed in a way that now favors “building” over “buying.” There are now ways of custom-developing systems that preserve many of the advantages of buying off the shelf. The these types of feedback increase the velocity of development without anyone working any faster! Part Three? Risk: The presence of uncertainty is the simple reason why Agile approaches work better than plan- decisions under uncertainty, and then have the courage to face the consequences. Shadow IT: Agile ways of working support a community approach to IT, where IT leaders achieve their objectives by mobilizing0 码力 | 7 页 | 387.61 KB | 5 月前3
MITRE Defense Agile Acquisition Guide - Mar 20142001, when 17 leading software developers created the Agile Manifesto to design and share better ways to develop software. The values and 12 principles of the Agile Manifesto can be distilled into four 15-minute) stand-up meeting. Each team member identifies his or her contributions by answering three questions: 1. What did you do yesterday? 2. What are you going to do today? 3. What obstacles operational and programmatic constraints, risks, and objectives. The figures below show potential ways to structure releases and sprints for a government program. Figure 9 shows a six-month release0 码力 | 74 页 | 3.57 MB | 5 月前3
A Seat at the Table - IT Leadership in the Age of Agilitysmall teams to inspect and adapt rather than stick to a plan. Lean thinking gives that small team ways to speed up its inspecting and adapting process to maximize its impact. Continuous Delivery and DevOps exist: A requirement is a constraint. It is a way of saying “create value this way, rather than other ways.” Really, a requirement is a constraint masquerading as a decision. What we have traditionally maintenance. Dividing our IT spending into development and maintenance buckets leads to some ineffective ways of making decisions. A nod to the ancient Greeks and the tale of Theseus’s ship. A Better Way – The0 码力 | 4 页 | 379.23 KB | 5 月前3
My Take on Agile Coachingstate defined by Mihaly Csikszentmihalyi where individuals perform at an optimal level. There are three things necessary to achieve Flow, and they all fall in the role of the Agile Coach: 1. Activity have ability to interact freely with all levels of an organization Coach to your own strengths Three primary categories from the Agile Coaching Institute 1. Technical Mastery 2. Business Mastery0 码力 | 2 页 | 417.28 KB | 5 月前3
Predictably Irrationalwith the three firm deadlines got the best grade; the class in which I set no deadlines at all (except for the final deadline) had the worst grades; and the class allowed to choose their own three deadlines0 码力 | 3 页 | 234.46 KB | 5 月前3
Pomodoro Techniquelife. In this new edition of his groundbreaking classic work, Csikszentmihalyi demonstrates the ways this positive state can be controlled, not just left to chance. Flow: The Psychology of Optimal0 码力 | 3 页 | 289.16 KB | 5 月前3
Cynefin - Agile for Defenseplace Signifies the multiple factors in our environment and our experiences that influence us in ways we don’t understand Developed by David SnowdenFramework A model tries to represent reality Framework0 码力 | 17 页 | 3.75 MB | 5 月前3
共 13 条
- 1
- 2













