The Phoenix Project - Book Review Plot 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 new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to report directly to him and fix and agreed to by proper stakeholders. Attributions [1] Amazon, http://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/0988262509/[2] The Three Ways: The Principles Underpinning DevOps, Gene

Open Discussion on Project Planning Planning in an Agile Environment Key Tenets  Planning should focus strongly on the near term  Eliminate waste caused by planning for eventualities that never come

and reference data 4. Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration files 8. This also includes pre-production and build processes tests. Spread Testing Grouplet team approach. Google – single, share repository of billions of files. 50% of code is changed each month. 40K code commits/day, 120K automated test suites, 75M tests cases/day productivity – everyone works in common area, simpler commits, but each commit can break the entire project ii. When merging is difficult, less able to refactor due to potential rework and merge problems

Monitoring and analysis tools 6. Tutorials and standards ii. Google – Single repository with over 1B files and over 2B SLOC, over 25K engineers for every Google property d. SPREAD KNOWLEDGE BY USING AUTOMATED find and fix as part of their daily work 1. Facebook HipHop PHP compiler – resulted from hack day project. Small team refined it over 2 year period and allowed Facebook to handle 6X production load compared

each organization’s IT environment. “You never know less than on the day you begin your new project. Each incremental delivery / review cycle adds knowledge and provides insights that the team managers should first identify the best approach for the project as a whole and/or for any subprojects within it. This includes assessing the project’s volatility (to include requirements and technology) release team responsible for execution. The release team includes a core team composed of the project manager, product owner, tester, and system engineer, and a development team led by a scrum master

centralized planning that could then be used to set boundaries for developers when they began a project. In other words, a vehicle for control. But standardization also imposes costs by:  limiting agility possible solutions to a problem.  if we mandate that projects reuse code whenever possible, each project may have to spend time searching archives of available code to find something that is a near fit IT shares the traditional view of governance.  The basics of the [governance] process involve project sponsors (1) developing a formal proposal that incorporates estimated benefits, risks, and resource

Transparency 0 Ed Snodgrass Awesomeness through Stable Teams 0 Mike Ballou Open Discussion on Project Planning 1 Mike Ballou Contracting Agile Projects 0 Adam Raggett Agile Transparency 1 Nick Chris Bellar Ansible enables Agile 2 Darin Plum Agile Goals for 2015 2 Mike Ballou The Phoenix Project - Book Review 0 Andy Sedlacek Agile 101 for Defense 2 Mike Macaulay Navigating the Promised Land Jerry Koske The Process of Innovation 2 Nick Tuck XP Prctices 1 Mike Ballou Open Discussion on Project Planning 1 Adam Raggett Agile Transparency 1 Eric Collins The Servant: Agile Book Club 1 Nick

is getting in our way as we try to become Agile. This frame of reference includes the notions of project, systems, application, investment, architecture, skill set, and accountability. We have, to be honest of the term – the Enterprise Architecture. The asset view of IT will substitute for the outdated project view in my vision for what IT leadership must become. Uncertainty and Risk: Third, underlying all do things best?  What is the value of adhering to a plan that was made at the beginning of a project, when uncertainty was greatest? Business value is destroyed only when we substitute extensive planning

Versus Buy: In a world where IT capabilities were delivered as a single “product” at the end of a project, a “product” that then only required a bit of maintenance now and then, the economics of IT delivery uncertainties are not small potential deviations from the initial plan—they are the very substance of the project. The Agile way to deal with uncertainty is to create options and then “buy” information to more worried about the schedule for delivering what they think of as FOC. The perceived risk is that the project will be “finished” late.  This, as we know, is based on the outdated idea that we define the scope

Transparency Ed Snodgrass Awesomeness through Stable Teams Mike Ballou Open Discussion on Project Planning Mike Ballou Contracting Agile Projects May 2014 Adam Raggett - Darin Plum Agile Goals for 2015 Mike Ballou The Phoenix Project - Book Review Andy Sedlacek Agile 101 for Defense Mike Macaulay Navigating the Promised Land