Joe Mcgrath, scrum master and coach in his latest blog explained the Lego Flow Game.
InfoQ interviewed Jan van Moll about regulatory demands for software in healthcare, satisfying these demands with waterfall project or with a mix of waterfall and agile, and introducing agile in an R&D organization that needs to fulfill regulatory demands.
To thoroughly remove waste in a process you need flow to deliver just in time, and mindfulness and situational awareness in organizations to handle problems with processes and built in human intelligence. Organizations apply concepts from flow to develop what is needed and when it is needed and use pull to prevent inventories. What they also need is “Jidoka”: mindfulness and situational awareness.
Agile testing can be used when developing software for automotive systems. To adopt agile techniques in automotive the automotive SPICE V-model needs to be adopted to agile. One result from combining agile and SPICE as Xavier Martin presented at the QA&Test 2014 conference is that “intensive automated testing and client demonstrations helps to produce better products, rising clients satisfaction”.
Testing teams and their managers need to unlearn the traditional mindset and practices when they want to adopt an agile way of working says Navneet Goyal. At the International Conference on Software QA and Testing on Embedded Systems he gave a talk about how test teams should adapt themselves in agile projects.
The 2014 CAST Research on Application Software Health (CRASH) report states that enterprise software built using a mixture of agile and waterfall methods will result in more robust and secure applications than those built using either agile or waterfall methods alone. InfoQ interviewed Bill Curtis about structural quality factors, and mixing agile and waterfall methods.
Agile software development is sometimes perceived as an undisciplined way of working. There are organizations which use that perception as an excuse to not adopt agile. According to others agile is actually a more disciplined approach than waterfall for software development. Let’s explore how discipline plays a role in agile and why discipline is considered important for agile to be successful.
Management can get the feeling of losing control when their enterprise adopts agile and starts deploying self-organizing teams. Procedures, review boards and consultation bodies can become superfluous when switching to an agile approach, but they may not realize that, says Marcel Heijmans. Trying to regain control with additional planning can make things worse, causing "death by planning".
This article includes advice for doing enough up-front architectural design to provide the needed structure to start a project, aligning the team with the architect’s vision and assessing the possible risks.
Organizations adopt agile to be able to handle changes. Agile helps teams to deliver products that satisfy the needs of customers; products which do not contain unneeded (and unused) features. Lean software development says: everything not adding value to the customer is considered to be waste. How can a transition from waterfall to agile software development help organizations to reduce waste?
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 series of recent articles by Steve Denning on Forbes have highlighted the challenges that the Agile community faces to get acceptance by mainstream management.
Scott W. Ambler provides some analysis on the latest Agile State of the Art survey. InfoQ follows up with some other insights and questions.
Scott Ambler published the results of his annual IT project success survey, in which he examined the impact of methodology on project outcome. He looked at five different "development paradigms" and how they influence project outcome: ad-hoc, iterative, traditional/waterfall, agile and lean. Ambler's definition of success is deliberately subjective - how did the customer feel about the outcome?
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.