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

*Tricentis 2021 Report: How The World's Top Organizations Test7 Aurora Innovation Agenda What is continuous regression testing How does regression testing work in practice How to build a regression testing Aurora Innovation Everything could go wrong “The inherent complexity of the real world and the continuous change of requirements result in large and complex software systems that are costly and dif�cult con�dence "Write tests. Not too many. Mostly integration." - Guillermo Rauch17 Aurora Innovation Continuous regression testing Continuously verifying that the software works as well as before, during the

4About Me Other interests: Game engines Meta-programming 5Robot path planning 6Robot path planning Path planning 7Path planning How an (autonomous) agent figures out how to get from one location to level goals of this talk Implement cache-friendly path planning code in C++ 29High level goals of this talk Implement cache-friendly path planning code in C++ Do so using the STL 30High level goals of Implement cache-friendly path planning code in C++ Do so using the STL Try to keep our choices simple 31High level goals of this talk Implement cache-friendly path planning code in C++ Do so using the

simulation ○ Wheeled robots: navigation, localization, 3D perception ○ Robotic arms: control, motion planning ○ Tooling: logging, data visualization ● I love C++, and I learnt a lot thanks to CPPCon videos

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

platform 02 03 04 Code reuse through libraries Building correct, secure, and safe systems Planning for the future Agenda Resources for learning modern C++ 0501 Obtaining tools for your platform platform 02 03 04 Code reuse through libraries Building correct, secure, and safe systems Planning for the future Agenda Resources for learning modern C++ 05Tools for your platform Build & platform 02 03 04 Code reuse through libraries Building correct, secure, and safe systems Planning for the future Agenda Resources for learning modern C++ 0501 Obtaining tools for your platform

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