InfoQ Homepage Methodologies Content on InfoQ
-
How No and Low Code Approaches Support Business Users and Professional Developers
No code approaches aim to support business users in developing and maintaining their own applications, where low code simplifies the developer’s work and makes them more productive. Both approaches enable faster development at lower costs. As the distinction between these approaches is becoming smaller, business users and developers can team up and use them together.
-
First Annual Retrospective Report Published
The First Annual Retrospective Report provides a deeper understanding of how retrospectives are used in the real world. The results indicate that retrospectives lead to improved team communication and productivity and help to create an environment of trust. Major challenges are that topics discussed cannot be solved by the team and people do not feel comfortable speaking up.
-
Strategy for Mobile and Web Test Coverage
Teams need to match testing with the market usage patterns across geographies of their apps as consumers are expecting smooth apps functionality across all digital channels. Here's a methodology and index for considering device/OS combinations together with other characteristics like aging, screen parameters and other testing related guidelines for data driven test coverage of the mobile market.
-
GitLab Survey Highlights Some Trends among Developers
GitLab has released the outcomes of a survey they conducted among software professionals from 362 startups from July 6 through July 27. Main highlights are developers' preference for using latest tools and more collaboration; security is high-priority, but 81 percent admitted to releasing software before it’s ready.
-
Achieving Cloud-Native Operability
To drive operational maturity you need a microservices architecture, continuous delivery process, DevOps culture and platform automation. Together these four help you to transform your whole organization for achieving cloud-native operability to continuously deliver additional value to your customers.
-
Don't Copy the Spotify Model
The Spotify model can help you to understand how things are done at Spotify, but you shouldn’t copy it in your own organization. It changes all the time as people at Spotify learn and discover new things. There is no one way in which software is developed at Spotify.
-
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.
-
Benefits of Agile Transformation at Barclays
Increased throughput, reduced code complexity, less production incidents, shorter deployment cycles and higher happiness in teams; these are some of the benefits that the agile transformation at Barclays has delivered. Within the first year of the transformation, which is based on Disciplined Agile, more than 800 teams adopted agile making this one of the largest agile implementations.
-
“It’s Not Just Microservices”: Fred George Discusses Technology, Process and Organisation Inhibitors
At the microXchg 2016 conference, Fred George presented “It’s Not Just Microservices”, and argued that microservices can enable an organisation to ‘go faster’ and rapidly deliver business value. However, the implementation of microservices alone will not lead to success, and inhibitors to increasing business agility within the context of technology, process and the organisation must be removed.
-
Road Mapping Your Way to Agile Fluency
Kelsey van Haaster will give a talk at 1st Conference about how to develop a road map to agile fluency for teams and organisations. InfoQ interviewed her about the possible ways to do an agile fluency assessment, example of findings and improvement opportunities that came out of the assessments and things that she learned, and advice for readers who want to use the agile fluency model.
-
Software Industry Pioneer Ed Yourdon Dies
Software industry pioneer, prolific author, researcher, consultant and photographer Edward Yourdon died on January 20, 2016
-
Scaling Without Blueprints and the Agile Scaling Cycle
InfoQ interviewed Stefan Roock about adding XP practices to Scrum, why using an agile framework as a blueprint for designing the organization is a premature optimization and why culture and principles are more important than practices. Roock also explains the agile scaling cycle with examples of how it can be used, and talks about the benefits and pitfalls of this approach for agile scaling.
-
Having the Right Mix of IT, Culture and Practice for DevOps
An interview with Nicole Forsgren about why organizations are starting to embrace DevOps methods, how being able to deploy fast can also increase IT stability, what to focus upon when changing the organizational culture to improve performance, how lean management can help to increase the performance, and asked her for advice when organizations want to apply DevOps to increase their performance.
-
Agile Testers can be a Harlequin
Agile testers can signal and question the (testing) process. Marnix van den Ent gave a talk at the Agile Testing Days 2015 in which he explained how he views testers as a harlequin: "a servant to the team and its process, like the Italian Harlequin he is there to help to understand what is happening". An interview about developing an art of questioning, XP practices and retrospectives.
-
Uncle Bob Proposes an Oath to Programmers
Uncle Bob proposes an oath to software programmers as other professions have, considering the importance of this craftsmanship.