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 Streamline processes to enable rapid and frequent delivery of capabilities Planning DOs and DON’Ts  DO establish some high-level planning, requirements, processes, and structure; however, activities focus concisely define the desired system functions and provide the foundation for Agile estimation and planning. o They describe what the users want to accomplish with the resulting system. User stories help

involving users throughout development to ensure high operational value Agile practices integrate planning, design, development, and testing into an iterative lifecycle to deliver software at frequent intervals Structure and Processes for Agile Development ............................................. 15 7 Planning ............................................................................................... Figure 2 - Basic Agile Structure Enabling an Agile environment demands some degree of up-front planning and design, but the method emphasizes the importance of beginning development quickly. The fundamental

and abuse. I have so much fun working alongside you.” – Mark Schwartz Last Time in Part One Planning: The idea that we should make a plan and then stick to it is a terrible idea in an environment Agile fellows. In the past: We viewed EA as primarily concerned with standardization, consistency, planning, and cost reduction. It documented as-is and to-be architectures, demonstrated alignment of systems systems with business needs, and did the “rigorous” up-front analysis and centralized planning that could then be used to set boundaries for developers when they began a project. In other words, a vehicle

gives that small team ways to speed up its inspecting and adapting process to maximize its impact. Continuous Delivery and DevOps place the entire value stream in the hands of that small team so that it can the current process, roles, responsibilities, and titles 4. Encourage leadership at all levels Planning Espousing the Wrong Values: The real reason we should reject the plan-driven approach to IT is when we substitute extensive planning for execution and when we substitute execution according to plan for thinking and adapting. A Better Way to Plan: Nevertheless, planning is important. In my role, I

Topic Nov 2015 Vote Tally Mike Ballou Agile Principles 0 Nick Tuck XP Prctices 1 Shawn Stumme Continuous Delivery 4 Josh Wade Cyber Security through Agile 2 Nick Tuck Maximizing Retrospectives 2 Ray 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 Wenner Clean Version Control Comparison 1 Dr. Mark Roth Release It (Agile Book Review!) 1 Ray Page Release Planning 2 Darin Plum Agile Coaching 5 Nick Wenner Clean Coder (book review) 2 Josh Sagucio Collaborative

delivery often favored buying a product off the shelf. But when we view IT capabilities as being in a continuous state of transformation, when we see them as tightly integrated into an EA, and when we realize accomplish those objectives. When combined with Agile and Lean practices, this approach can focus IT planning, reduce risk, eliminate waste, and provide a supportive environment for teams engaged in creating to more accurately assess probabilities. Traditional teams attempt to drive out uncertainty by planning and analysis. Agile teams tend to drive out uncertainty by developing working software in small

work by implementing continuous delivery i. Create the foundation of our deployment pipeline ii. Enabling fast & reliable automated testing iii. Enabling & practicing continuous integration & testing results, environments deployed to, etc. a. Use to support audits and compliance iv. Create out continuous integration practices 1. Comprehensive and reliable automated tests to validate deployable state ii. If not, undoes the work done to get to a known workable state 4. Ch. 11 Enable and Practice Continuous Integration a. Branching – Pros & Cons i. Pro – Allows work in parallel while minimizing potential

Automate as much of the development and deployment activities as possible.  Adopt common tools from planning and requirements through deployment and operations.  Leverage agile software principles and favor sets of Development, Cybersecurity, and Operations throughout the software lifecycle, embracing a continuous monitoring approach in parallel instead of waiting to apply each skill set sequentially.  Security management, a zero-trust model, a whitelist, Role-Based Access Control (RBAC), continuous monitoring, signature-based continuous scanning using Common Vulnerabilities and Exposures (CVEs), runtime behavior

herel!l Feb 2014 Mike Ballou Agile Principles Nick Tuck XP Prctices shawn stumme Continuous Delivery Josh Wade Cyber Security through Agile Mar 2014 Nick Tuck Snodgrass Awesomeness through Stable Teams Mike Ballou Open Discussion on Project Planning Mike Ballou Contracting Agile Projects May 2014 Adam Raggett Release It (Agile Book Review) Aug 2014 Ray Page Release Planning Darin Plum Agile Coaching Nick Wenner Clean Coder (book review)

got better  We read and we studied.  Created a self-improvement project  2 week iterations, planning and demos  Put everything into a repository (configurations, scripts, etc.) Infrastructure as Practice, etc.  Test Driven Infrastructure  Blue – green deployments  Combining DevOps Scrum – planning, standups, boards, and backlogs  Making work visible (it’s still hidden)  Poor measurements Lean & Agile Development: Thinking & Organizational Tools for Large-Scale Scrum, Craig Larman  Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, Jez Humble