Often teams first begin their agile journey with an iteration-based methodology, such as Scrum. This is because the dependable cycle of iterations that these methodologies impose on teams introduce a feeling a stability and predictability. However, after a team finds success with an iteration-based methodology, it’s often not long

Many agile teams have become obsessed with speed. How fast can we release? How fast can we close stories? How fast can we deliver to market? What too few fail to realize, however, is that none of this speed matters unless what the team is delivering is actually providing value

Few would argue with the benefits that can be gained from a switch to an agile approach. Agile teams enjoy more autonomy and greater fulfillment from their jobs while organizations enjoy faster time to market and and an increased ability to respond to the emerging needs of their customers and

Throughout our Getting Started With Agile series, we’ve dove deeply into each of the 4 main values of the agile manifesto. During this dive, we’ve unpacked not only the intent behind each value but also the underlying ideas and concepts that led to the creation of that value.