BT

InfoQ Homepage Software Craftsmanship Content on InfoQ

  • Why Self-Organisation is Intuitive, Yet Challenging to Adopt

    Self-organisation can be challenging; you need to understand what's required to achieve, and success needs to be visible, said Mirco Hering, managing director at Accenture. He suggested to create boundaries in which to self-organise and enrich the team’s context, showing how well they are doing.

  • Quality and Culture: Learnings from Other Disciplines and Industries

    We can gain by learning about other industries such as aviation and healthcare, and studying other disciplines, argued Conor Fitzgerald, software tester at Poppulo, at RebelCon.io 2019. Aviation has a history of continually learning from its mistakes, whereas in healthcare, culture and bias seem to challenge learning and continuous improvement.

  • Experience Building a QA Team in a Growing Organization

    Shifting the test team to the left brought the whole team closer together, enabled faster learning, and improved collaboration, claimed Neven Matas, QA team lead at Infinum. He spoke at TestCon Moscow 2019 where he shared the lessons learned from building a QA team in a growing organization.

  • Optimize Automated Testing Using Defect Data

    By integrating the test framework and the bug tracking system, it becomes possible to deactivate test cases for known bugs and reactivate them when the bug is solved. Aneta Petkova, QA chapter lead at SumUp, presented The Framework That Knows Its Bugs at TestCon Moscow 2019.

  • Investigating Near Misses to Prevent Disasters: QCon London Q&A

    Investigating near misses by gathering data from the field and exploring anything that looks wrong or is a bit odd can help to prevent disasters, said Ed Holland, software development manager at Metaswitch Networks. At QCon London 2019 he gave a talk about avoiding being in the news by investigating near misses.

  • Building High-Quality Products with Distributed Teams

    To ensure the quality of the products and services, Intermedia uses a common test & pre-production environment for all distributed teams. Lilia Gorbachik, product manager at Intermedia, mentioned at European Women in Tech that having a mature testing process, working with risks, and making daily decisions from a high-quality product perspective are key aspects to build high-quality products.

  • The Tech Coach Strikes Back: The Value of Mentoring and Mob Programming

    Technical coaching is all about helping developers grow by finding ways to increase their technical excellence and to work with softer skills, like the ability to be able to communicate and listen to other developers, argued Tobias Modig at GrowIT 2018. The softer part is closely connected to traditional coaching, but it also comes with a tech twist.

  • The Manual Regression Testing Manifesto

    Automating regression tests isn’t always the best solution, argued Brendan Connolly at the 2018 fall Online Testing Conference. He presented the “manual regression testing manifesto” and showed how it can be used to differentiate feature testing from regression testing and to decide when to automate or not automate tests.

  • Underplayed Premises of TDD: Q&A with GeePaw Hill

    TDD is more than a technique; it’s a whole style of programming, an integrated system of related behaviors and ideas. The five premises of TDD provide a ring in which we operate, they are the air that a TDD’er breathes.

  • Code Reviews in Practice

    Code reviews are a great way to find bugs, get input from other team members, and share knowledge and ownership. For maximum benefit, integrate code reviews into your development process to ensure that no code reaches production without being reviewed. Reviews tend to uncover unresolved issues in the development process which you may need to address.

  • Readable Code - Why, How and When You Should Write It

    Most people would say they want readable code, and may even prefer readability over functionality. But when it comes down to asking people to define readability, opinions will start to diverge. At Explore DDD 2018 , Laura Savino covered why we want readable code, what it really means to be readable, and when readability absolutely must take priority over other considerations.

  • Focusing on Business Outcomes at Barclays: Overcoming the "Urgency Paradox"

    Jonathan Smart, head of working ways, and Morag McCall, PMO at Barclays, spoke last month at the DevOps Enterprise Summit in London about re-thinking the entire flow of work, from initial idea triage until releasing to production. This means introducing agility into how the application and services portfolio is managed, as well as changing the role of the PMO and finance departments.

  • Getting More Work Done in Fewer Working Hours

    When Jason Lengstorf’s body was actively falling apart due of the way he was working, he decided to limit his computer usage and create pockets of high-focus effort. Working fewer hours prevents you from becoming overtired or unfocused. We need to treat downtime with the same level of care as we treat our uptime, using breaks to make creative connections, recharge, and to remember why we work.

  • Sustainable Software with Agile

    Sustainable software enables you to deliver changes to the customer more quickly with a lower likelihood of bugs, decrease of the total cost of ownership of applications, and increase business agility. It’s possible to verify the sustainability of software using a combination of automated analysis of source code, expert review of technical artifacts, and comparison with benchmark data.

  • Software Engineering for Creativity, Collaboration, and Inventiveness

    A software engineering discipline must be iterative, based on feedback, incremental, experimental, and empirical. Craftsmanship is not sufficient; engineering is an amplifier, it enhances creativity, collaboration, and inventiveness. Continuous delivery is grounded in engineering principles.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.