BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Complex Systems Content on InfoQ

  • Rebuild or Refactor?

    Should you rebuilding or refactoring software?An interview with Wouter Lagerweij about what it is that makes refactoring so difficult, if rebuilding software is less risky than refactoring, and how continuous delivery fits with rebuilding software.

  • Deploying Scrum and SAFe at Philips Lighting

    InfoQ interviewed Frank Penning, PMO manager from Philips Lighting, about the main challenges that Philips Lighting is facing in product development, why Scrum is not enough, how they apply SAFe, and the benefits that they have gained from deploying agile methods for product development.

  • Scaling Dilemmas and How to Deal with Them

    Making teams working together can be challenging, but it is often needed to develop and deliver large complex products. In her opening keynote about scaling dilemma's at the Agile Adria 2015 conference Mary Poppendieck presented ideas for organizations that want to scale agile.

  • Mary Poppendieck Discusses Containers, Microservices and Contract Tests

    At Craft Conference 2015 in Budapest, Mary Poppendieck discussed the ‘new software development game’ and offered advice on how best to utilise containers, microservices and consumer-based contract tests to lower friction and limit risk within software systems.

  • Experiment using Behavior Driven Development

    Behavior Driven Development (BDD) uses examples, preferably in conversations, to illustrate behavior. A lot of people focus on the tools if they are doing BDD but having the conversations is more important than writing down conversations and automating them said to Liz Keogh. An exploration of using BDD to do experiments to deal with complex problems and do discoveries.

  • Managing the Expectations from Agile

    InfoQ did an interview with Gil Zilberfeld about managing the expectations that organizations have of agile and how to prevent misconceptions, valuable ideas and practices from agile and what the future will bring for agile.

  • Systems Thinking for Safety Keynote @ Velocity Conf

    The starting keynote at Velocity Conference Europe 2014 was all about how human error is too often the easiest way to explain away a failure and how a different approach is needed. Steven Shorrock, European Safety Culture Programme Leader at Eurocontrol, explained why a Systems Thinking approach applied to safety is a better answer.

  • 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.

  • Using Complexity Measurements to Improve Software Quality

    Complexity is a direct indicator of software quality and costs: if the complexity for any code is high, the quality of that code will be lower and it will cost more to manage it. Complexity measurements can be used to estimate development and test activities and to decide where refactoring is needed to improve quality and prevent problems.

  • Testing Machine to Machine Systems

    Devices are becoming increasingly interconnected through the internet where they are communicating directly with each other. Testing such machine to machine (M2M) systems can be difficult due to their complexity and the usage of different platforms, as Peter Varhol explained in his talk about testing in the M2M world at the QA&Test 2014 conference.

  • Applying Use Cases in Agile: Use Case 2.0, Slicing and Laminating

    To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.

  • Sound of Silence: A workshop for Improving Understanding and Listening

    At the Agile Tour Brussels conference, Luc Taesch facilitated a workshop about understanding and listening. He applied "cognitive science" or "neuroscience" for IT Professionals, and provided solutions to help them dealing with interrupting thoughts and feelings.

  • Simplicity for Building the Right Thing

    At GOTO Amsterdam 2013, Russ Miles did a lightning talk about building the right thing in 5 questions: the 4 questions from impact mapping “Why? Who? How? and What?” and one additional question “What assumptions underpin everything?”. InfoQ did an interview with him about building the right thing using simplicity.

BT