BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Sustainable Pace Content on InfoQ

News

RSS Feed
  • How a Sustainable Mindset in Software Engineering Can Increase Team Performance and Prevent Burnout

    A sustainable mindset in software engineering matters because software is still primarily built by humans, and we must prioritize their well-being, Marion Løken said at NDC Oslo. Integrating the team more deeply into discovery work, discussing feedback collectively, and fostering a culture of psychological safety helped to engage her team and mitigate burnout.

  • How to Work Asynchronously as a Remote-First SRE

    The core practices for remote work at Netlify are prioritising asynchronous communication, being intentional about our remote community building, and encouraging colleagues to protect their work-life balance. Sustainable remote work starts with sustainable working hours, which includes making yourself “almost” unreachable with clear boundaries and protocols for out of hours contact.

  • Enabling Agile Teams to Improve Software Quality

    Long working days, deadlines and team pressure can impact the quality of the software that agile teams deliver. What can we do to prevent that from happening and enable teams to improve the quality of their software? Some suggestions are to arrange for scope and deadline slack, adopt pull systems, and to make sure that people can slow down and get enough sleep.

  • Sustainable Pace, How to Achieve and Improve it?

    Being one of the principles of the agile manifesto, sustainable pace is considered important by many to deploy agile. But achieving a sustainable pace can be difficult, and teams are often asked to improve their velocity. What did you do to adopt sustainable pace with your team? And how did you improve the speed in which your team delivers, and establish a new sustainable level?

  • Taking a Break From Sprinting

    Over the long term, can teams sustain constant work on the product backlog? If a break is needed, what's the most effective way of doing it?

BT