Agile Principles Agile Spike An Agile Spike is used whenever a team is faced with implementing a solution that is not fully understood. A team may be struggling with a number of issues such as the amount of traffic a solution will see or the number of users that a solution will have. A Spike is a pilot project that attacks risk. Agile Spikes are always time boxed to reduce the risk of scope creep and keep our project on schedule. Whenever a team is faced with uncertainty when implementing a solution, Agile teams will look to create a Spike. Essentially what we do is create model architecture of our solution with our best guesses on how the system will behave. Once the Spike is developed, we can watch and observe this model to better understand how the real solution will behave in production. Our goal is to understand how it is going to behave and learn any early lessons before we begin the real project. Simple design Security teams are under constant pressure to improve the security landscape of an organization. Usually, while faced with low budgets and resources, a primary practice in Agile IT Security is to keep our solutions as simple as possible. We also don't need to fully understand the solution or countermeasure in detail before we begin. We can learn and change as we build the solution. Look for models and solutions and how the industry at large is solving the problem at hand. Talk to experts in the field to see what solutions are recommended to solve the problem. Once we have a basic idea of what we want we can start to implement the solution. Keep in mind that the solution can and will change and we can always change the