InfoQ Homepage Culture & Methods Content on InfoQ
-
Improving Corporate Cognitive Performance in IT Organisations
The biggest tool in the software engineer’s toolkit is the brain, yet few organisations go out of their way to educate and create the conditions in which the brain can work at its best. Explore the different domains of the brain and their links to the performance of software engineers and see what organisations can do to create workplaces that propagate advanced levels of cognitive performance.
-
Engineering Culture and Distributed Agile Teams
Franzen and Pahuja explain how a distributed agile framework can help distributed teams create an engineering culture based on over a decade of experience, and share actionable practices that help you get your distributed engineering tools and practices in place. Topics covered are devops, team structure, microservices, pair programming, T-shaped engineers, continuous integration and deployment.
-
The Burger House: A Tale of Systems Thinking, Bottlenecks and Cross-Functionality
A small, upscale burger house opens on a narrow street of Rio de Janeiro. Their system is optimized for efficient order taking. However, unfortunately, it is chaotic. One morning, a cashier did not come to work. Can you guess what happened? With a little help from the Theory of Constraints and Systems Thinking, we will explain in this article why their system actually improved one person short!
-
Oldies in Tech: Hiring and Getting Hired
Denoncourt gives advice to older job seekers with tips on how to go about writing cover letters, filling out resumes, handling themselves in interviews, and preparing for difficult questions and coding assessments. Employers will change their perspective of older applicants and see the benefits of hiring sage programmers that are smart, love learning and have a track record of success.
-
Q&A on the Book Working with Coders
The book Working with Coders is a practical guide to managing teams of software developers aimed at a non-technical audience. In the book, Patrick Gleeson explores how the software development process works and what managers can do to support it effectively and build solid working relationships with coders.
-
Six Ways Agile Can Turn Static
Agile development in the right circumstances enables organizations to release high quality software that changes rapidly to drive businesses forward. It just doesn’t work all the time. Success requires collaboration, transparency and real-time visibility into project risk and quality.
-
The Seven Steps to Building a Successful Software Development Company
Building a successful software development company is hard. There are lots of challenges and barriers that need to be overcome. This article provides seven things that can help start on the right footing and keep on track for success. Build the right team, have a clear focus, leverage partnerships, nurture and protect your culture, identify and leverage new technologies and look to the finances
-
Transcend the “Feature Factory” Mindset Using Modern Agile and OKR
Using Agile with waterfall goals turns teams into "feature factories" with no focus on delivering value. To transcend this mindset, companies can apply Modern Agile’s four principles by using OKR (Objectives and Key Results). Combining Modern Agile with the proper use of OKR can be a lightweight way for organizations to give teams the autonomy to experiment and achieve awesome results.
-
Six Pointers for Creating Strong Operational Business Values
A system that is flexible and open to inputs works for organizations of all sizes. This article is a rulebook for leaders on how to create a values-driven culture that not only lifts a new business off the ground, but also keeps it going in the long run, by encouraging creativity, an ownership mentality, honesty in feedback, and open communication across the board.
-
Perspective on Architectural Fitness of Microservices
In this article we peel the onion of potential architectural fitness of microservices in the context of Master Data Management, and the challenges a microservices-based architecture may face when solving problem domains that require compute-intensive tasks, such as the calculation of expected losses on a portfolio of unsecured consumer credit.
-
Q&A on the Book "The Stupidity Paradox"
In "The Stupidity Paradox", Andre Spicer and Mats Alvesson explore how knowledge intensive organizations employ smart people and encourage them to do stupid things. Functional stupidity can be catastrophic, however a dose of stupidity can be useful. The book advises how to counter stupidity or reduce the consequences, how to exploit it, and how to benefit from it.
-
Automated Journey Testing with Cascade
Starting with a brief history of software testing, we investigate Cascade, a new framework for testing “journeys”, eliminating overlapping coverage to produce fast unit tests.