InfoQ Homepage Culture & Methods Content on InfoQ
-
/articles/continuous-delivery-coding-patterns/en/smallimage/logo.jpg)
Continuous Delivery Coding Patterns: Latent-to-Live Code & Forward Compatible Interim Versions
This article describes two novel practices for continuous delivery: Latent-to-live code pattern and Forward compatible interim versions. You can use these practices to simultaneously increase speed and reliability of software development and reduce risks. These practices are built on top of two other essential continuous delivery practices: trunk-based-development and feature toggles.
-
/articles/technical-hack-conciousness/en/smallimage/logo.jpg)
Technical Practices as a Hack on Consciousness: Why to Hack Yourself
Software technical practices are usually adopted as a means of creating better products. These practices can create and maintain a healthy human system. Technical practices raise the consciousness of individuals and the team as a whole. Technical practices hack consciousness giving us a quick, deep chute into depths of connection that improve our selves, our products, and our world.
-
/articles/agile-critical-millennial/en/smallimage/agile-logo.jpg)
Why Agile Is Critical for Attracting Millennial Engineers
More and more companies are realizing that having an Agile organization is critical to attracting and retaining the latest generation of millennial engineers. Millennials demand the context, flat organization/decentralized power and emphasis on collaboration that Agile offers – and companies of all sizes and verticals are responding.
-
/articles/what-agile-mindset/en/smallimage/logo-agile.jpg)
What Exactly is the Agile Mindset?
We hear, and even use, the phrase “agile mindset.” But what is it, really? In this article several themes are identified, such as respect, ability to change, and focus on delivering value. Additionally, possible methods for introducing and nurturing these themes are identified.
-
/articles/christine-doig-data-science-team-discipline/en/smallimage/data-logo.jpg)
Christine Doig on Data Science as a Team Discipline
Christine Doig spoke at this year's OSCON Conference about data science as a team discipline and how to navigate the data science Python ecosystem. InfoQ spoke with Christine about challenges data science teams need to address to be more effective.
-
/articles/book-review-effective-debugging/en/smallimage/cover.jpg)
Q&A with Diomidis Spinellis on Effective Debugging
The book Effective Debugging by Diomidis Spinellis describes 66 different approaches for effective debugging of applications and systems. It provides methods, strategies, techniques, and tools for finding and removing faults, and gives examples for using them in different settings.
-
/articles/how-make-agile-successful/en/smallimage/logo.jpg)
So, How Do You Make Agile Successful?
It is not Agile's fault, it is your fault - Are you fed up with such statements? This article tries to provide a more constructive answer on how to make Agile successful. It first shows how Scrum can be harmful, then argues how Agile requires different skills on both product and delivery levels. It suggests to use CICD to counteract Scrum's traps and stresses the importance of systems thinking.
-
/articles/how-startups-build-software/en/smallimage/HiRes.jpg)
How Startups Get Software Built
For most startups, technology is a critical differentiator—the bridge between a consumer’s pain puddle and a startup’s revenue stream. The software is the thing that gets the idea off the cocktail napkin and into the customer’s hand. How do startups do it right? Fail, pivot, fail, pivot, repeat forever (and do it all FAST).
-
/articles/wtf-requirements-agile/en/smallimage/logo-agile.jpg)
WTF requirements in Agile Product Development
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
-
/articles/waterfall-requirements-agile/en/smallimage/logo-agile.jpg)
Waterfall Requirements in Agile Product Development
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
-
/articles/decoding-silicon-valley/en/smallimage/wesheadshot-horizontal.jpg)
Author Q&A: Decoding Silicon Valley
Jon Baer and Michelle Messina have written a book exploring the secrets to success in Silicon Valley - what it takes for a startup to succeed. They look at the culture, history and stories which show how and why the Valley works, and provide guidance for prospective entrepreneurs who are considering setting up in the Valley, or elsewhere. They spoke to InfoQ about the book and their ideas.
-
/articles/stop-measuring-turn-around/en/smallimage/agile-logo.jpg)
Stop Measuring Turn Around Time
Are you patting yourself on the back for remarkable turn around times while simultaneously neglecting your customers? It's tempting to think that timeliness matters when in fact it rarely does. Stop measuring turn around time and start learning what matters to customers.