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

universe, we must interface Grok with the world… …As a first step towards this vision, we are rolling out DeepSearch – our first agent. It's a lightning-fast AI agent built to relentlessly seek the refers to systems capable of performing the full range of human intellectual tasks – reasoning, planning, learning from small data samples, and generalizing knowledge across domains. Unlike current AI access, then toward distribution / scale, and now toward computation / intelligence. The earliest wave saw CapEx pouring into building internet infrastructure – massive server farms, undersea cables,

Acquisition) https://www.acq.osd.mil/evm/ Incremental process, i.e. Rolling Wave Planning; Agile Release/Program Increment Planning. Scenario describes one method of how Agile can underpin EVM progress

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

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 them. I want to make sure the team has a good basis for making value decisions.  How is the team planning to work together? What skills are on the team? How will the team communicate? How do they plan

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

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 Overview 2 Brandon McAllister Automation 2 Ron Horner Kanban for the People! 2 Ray Page Release Planning 2 Nick Wenner Clean Coder (book review) 2 Scott Grimes Agile Certifications 2 Jason Smith Empowering

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 scenarios as the future unfolds.  Jez Humble and his co-authors suggest that instead of using detailed planning to manage risk, we instead use experiments.  When we encounter a risk, we should think of something

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