A Tale of Two Companies is a narrative story about two companies who are facing competition from new entrants into their business vertical and are looking to regain their competitiveness through Agile/DevOps. Along with the story of the two companies, there are learning points in each section. This book takes a very different tact then the majority of DevOps books on the market, the book attempts to explain in simple terms through Learning Points why, as Gartner has pointed out, 90% (the true number is probably higher) of the companies attempting DevOps are failing. A couple of sample Learning Points the book covers are below: Many in the industry have probably heard the reference to the “Blame Game”, which is the conflict between development and [...]
A common problem in the world of software development is bringing Technical Debt to the forefront so that organizations can clearly see why they need to make the move towards Agile and DevOps. The issue is, how do we get everyone in the organization on board? Even when you explain to the business side that research has shown that organizations of all types and sizes are having to spend 70% to 80% of their entire Software Development budget simply maintaining existing code, they don’t believe this includes them or they simply don’t fully understand the issue. The problem is that they see the requests they make to Software Development moving through the Software Development process and believe this is all new work being created for [...]
One of the starting points with any organization looking to start the DevOps journey or even just looking for process improvement is to create a current and future state Value Stream Map or apply the Theory of Constraints. The concept of Value Stream Mapping has been around for many years (possibly as early as 1918) and is usually associated with Lean. Value Stream Mapping can be used in conjunction with the Theory of Constraints or they may both be applied separately. Value Stream Mapping helps show how both materials and information flow as a product or service through the process value stream, helping teams visualize where improvements might be made in both flows. The Theory of Constraints is used to concentrate on reducing the throughput [...]
User Stories, where do they come from? How do you write them? What do you do with them once they are written? Check out this short presentation on The Life Cycle of a User Story and get some answers. To view more information on applying agile techniques by Kristen Varona, visit SCRUM Estimation.
Estimation is inaccurate by nature. Traditionally, hours and days have been used to provide an estimate. The problem encountered with using hours and days to provide an estimate is that they are absolute, even when given relatively, which inherently imply commitment. In an agile environment, we use a Story Point to provide an estimate. Story Points are relative and unit-less. For this reason, relative estimation doesn’t change over time and remains relative. Story Points typically follow the Fibonacci sequence (1, 2, 3, 5, 8, 13…) this limits the number of estimation choices encouraging a team to collaborate to come to an agreed upon estimate. Limited estimation choices speed estimations, promote consistency and become more accurate when triangulating against known user stories for comparison. During collaboration, [...]