existing Agile methods (e.g., Scrum, Extreme Programming (XP), Kanban, Test Driven Development) has its own unique processes, terms, techniques, and timelines. Because Scrum is the most widely used Agile Agile methodology, this guide uses Scrum terms and processes, but DoD could employ practices from all of these Agile methodologies. This guide addresses the distinct difference between a company employing Sprint - Priority capabilities developed, integrated, tested, and demonstrated (aka: iteration) Daily Scrum - Team synchronization meeting to plan activities and assess progress and impediments3 A release

change it? How do we encourage transparency, priori- ties, and accountability? You know the answer: Scrum. Let’s start a few thousand miles west of Washington, D.C., in the Washington state capital, Olympia SMART— Specific, Measureable, Attainable, Relevant, and Time-bound. In other words, they want to use Scrum. And, in fact, they are. The office of the Chief Information Officer of the State of Washington is how to implement state policy. To do that, they use Scrum. They’ve actually torn down the cubicle walls in their offices and formed into Scrum teams. Michael DeAngelo, the Deputy CIO, says they try

review) 0 Mike Ballou Pomodoro Technique 4 Steve Barr DevOps: A Horse's Perspective 1 Kyle Baardson Scrum - Doing Twice the Work, in Half the Time 1 Nick Tuck Assuring Quality 3 Toby Flint Lean Startup Retrospectives 2 Eric Ewing LeanUX - Book Club 1 Tek Agile Trends in the Industry 1 Sean Lomax Scrum: The Art of Doing Twice the Work in Half the Time 2 Craig Lacy Challenges to Adopting Agile in a Scott Grimes Technical Debt 2 Nick Wenner My Experience in Effective Retrospectives 2 Sean Lomax Scrum: The Art of Doing Twice the Work in Half the Time 2 Jerry Koske The Process of Innovation 2 Nick

Mary PoppendieckTeam -> Program -> Portfolio Team  Cross functional  Scrum  Release cadence  HIP Program  Built on Scrum, except scaled up  self-organizing, self-managing team-of-agile-teams

Pomodoro Technique Steve Barr DevOps: A Horse's Perspective Kyle Baardson Scrum - Doing Twice the Work, in Halfthe Time Mar 2015 Nick Tuck Assuring Quality - Tek Agile Trends in the Industry Sean Lomax scrum: The Art of Doing Twice the Work in Half the Time Oct 2015 Craig Lacy Challenges

of 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 Book List  Scaling Lean & Agile Development: Thinking & Organizational Tools for Large-Scale Scrum, Craig Larman  Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment

attendance data (attendance.daily_records). Deathstar Scrum Reports : Daily scrum reports from the teams working on the Deathstar (deathstar.scrum_reports). To keep the setup small, we will just launch which is the only pod that should be able to read all attendance data, or read/write the Deathstar scrum notes (label app=empire-hq). empire-outpost : A random outpost in the empire. It should be able to any keyspace, including the deathstar keyspace. For example, run: $ cqlsh> SELECT * FROM deathstar.scrum_notes; empire_member_id | content | creation -----

daily a�endance data (a�endance.daily_records). Deathstar Scrum Reports : Daily scrum reports from the teams working on the Deathstar (deathstar.scrum_reports). To keep the setup small, we will just launch which is the only pod that should be able to read all a�endance data, or read/write the Deathstar scrum notes (label app=empire-hq). empire-outpost : A random outpost in the empire. It should be able to any keyspace, including the deathstar keyspace. For example, run: $ cqlsh> SELECT * FROM deathstar.scrum_notes; empire_member_id | content -------------

attendance data (attendance.daily_records). Deathstar Scrum Reports : Daily scrum reports from the teams working on the Deathstar (deathstar.scrum_reports). To keep the setup small, we will just launch which is the only pod that should be able to read all attendance data, or read/write the Deathstar scrum notes (label app=empire-hq). empire-outpost : A random outpost in the empire. It should be able to any keyspace, including the deathstar keyspace. For example, run: $ cqlsh> SELECT * FROM deathstar.scrum_notes; empire_member_id | content | creation -----

attendance data (attendance.daily_records). Deathstar Scrum Reports : Daily scrum reports from the teams working on the Deathstar (deathstar.scrum_reports). To keep the setup small, we will just launch which is the only pod that should be able to read all attendance data, or read/write the Deathstar scrum notes (label app=empire-hq). empire-outpost : A random outpost in the empire. It should be able to any keyspace, including the deathstar keyspace. For example, run: $ cqlsh> SELECT * FROM deathstar.scrum_notes; empire_member_id | content | creation -----