InfoQ Homepage Waterfall Content on InfoQ
-
Simulating Agile Strategies with the Lazy Stopping Model
Simulation can be used to compare agile strategies and increase understanding of their strengths and weaknesses in different organisational and project contexts. The Lazy Stopping Model derived from the idea that we often fail to gather sufficient information to get an optimal result. Agile strategies can be simulated in the model as more or less effective defences against this “lazy stopping.”
-
2020 State of Testing Survey: Call for Participation
The 2020 State of Testing survey is now seeking participation, and aims to provide insights into how the testing profession develops and to recognize testing trends. Anyone completing the survey will receive a complimentary copy of the State of Testing 2020 report once it is published.
-
2019 State of Testing Survey: Call for Participation
The 2019 State of Testing survey is now seeking participation, and aims to provide insights into how the testing profession develops and to recognize testing trends. Anyone completing the survey will receive a complimentary copy of the State of Testing 2019 report once it is published.
-
How Agile and Architecture Parted and Finally Became Friends
People stopped seeing the need to define the architecture or do software design due to incorrect interpretation of the agile manifesto, argued Simon Brown. Many software developers don’t seem to have a sufficient toolbox of practices and the software industry lacks a common vocabulary for architecture. A good architecture enables agility with just enough up front design to create firm foundations.
-
The Lego Flow Game
Joe Mcgrath, scrum master and coach in his latest blog explained the Lego Flow Game.
-
Meeting Regulatory Demands with Agile Software Development
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.
-
Mindfulness and Situational Awareness in Organizations
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 for Automotive Systems
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”.
-
Adapting Test Teams to Agile Projects
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.
-
Mixing Agile with Waterfall for Code Quality
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.
-
The Importance of Discipline in Agile
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.
-
Death by Planning in Agile Adoption
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".
-
How to Do Just Enough Up-front Design
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.
-
Reduce Waste by Changing from Waterfall to Agile
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?
-
Survey Confirms Scaling Agile Across The Organisation Is Still A Challenge
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.