Many teams new to Agile start with Scrum. Scrum provides clear guidance, rules, and practices to help teams adopt an Agile mindset. It also surfaces a lot of problems in organizations, which is part of what makes it so difficult for many companies to do successfully. For those that have been doing Scrum for a while, the question becomes, what now? Is this all there is?.
The Wall Street Journal has begun to take notice of the growing number of technology companies that have been practicing Pair Programming and has published their take on the practice in an article titled Computer Programmers Learn Tough Lesson in Sharing.
In his recent blog posting “Theory of Constraints and Software Engineering” Steve Tendon addresses why throughput accounting should be preferred over cost accounting in software development organizations. He also provides a simple model for throughput accounting that is applicable to software engineering.
CW500 Club organised an event dedicated to the future of software development. Now you can find the presentations prepared by the speakers and a summary of the event on the Computer Weekly website.
For years, many people have considered Scrum to be the default starting point when talking about Agile implementations. However, with the recent rise of Kanban, some now see Kanban as the next step in the evolution of Agile.
The Lean Software & Systems Consortium (LeanSCC) whose mission is to improve the world by improving its systems and system-building capabilities (well known in the agile community for promoting the use of Kanban for software development) reorganized as the Lean System Society. The goal is to accelerate and deepen the Lean paradigm and bring together thinkers and doers from different perspectives.
Forrester have recently released the results of their November 2011 Global Agile Software Application Development Online Survey in a report entitled "Survey Results: How Agile Is Your Organization?" It contains a number of interesting findings around how organisations that have adopted Agile are dealing with their implementation.
A recent Harvard Business Review article highlights the importance of finishing one task at a time and hence getting more work done. Some of the core Agile practices help minimize context switching and bring a similar task focus while building software.
The Agile community has a great tradition of making fun of itself and April Fools Day 2012 was no exception. Here is a wrap up of some of the best gags from this year that you may have missed.
For years Agile has been encouraging teams to work together collaboratively in open spaces and encouraging developers to pair program, but lately these types of practices have been coming under fire.
Is the Lean Startup movement another fad or a real source of value creation? The implications of the latter are extreme. If Lean Startup is a real way to achieve consistent success in new ventures then Eric Ries may have cracked the code toward persistent venture success and ultimately: wealth creation.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
Scrum community leader Jim Coplien proposes One Piece Continuous Flow as an alternative to Kanban. He believes that a cross functional team should work together as a single unit instead of sub teams waiting for work items to arrive from previous stages. Kanban practitioners find their framework to be more usable in an environment where cross-functional teams are not readily feasible.
As western governments struggle with difficult debt to GDP ratios, the UK is turning to innovation and agile practices to help create a more efficient and less risky IT project delivery framework.
Agile Coaching often involves travelling outside of a coaches home town to whereever the client may be located. As a result, coaches may feel like they are working all the time. Is there hope for a work/life balance?