BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Scaling Content on InfoQ

  • Q&A on the Book Scaling Teams

    The book Scaling Teams by Alexander Grosse and David Loftesness provides strategies and practices for managing teams in fast growing organizations. It explores five areas which often pose challenges when organizations need to scale -- hiring, people management, organization, culture and communication -- and gives solutions for recognizing and dealing with those challenges.

  • Predictable Agile Delivery

    Human teams are unique, non-linear and unpredictable, but given the right conditions, their output can become linear, scaled and predictable. Managers have an enabling role to play: encouraging the development of predictability; understanding the needs of their teams; and rolling-up their sleeves to clear the blockages themselves or by escalating the problem promptly and responsibly.

  • Voys Learns to Play the Holacracy Game

    Holacracy removes power from a management hierarchy and distributes it across teams that have a clear set of roles, responsibilities, and expectations. This new organizational system with no managers or titles is often misunderstood. Learn about holacracy from the Dutch telecom company Voys who implemented this new way of running organizations.

  • Scrum Alone is Not Enough – An Interview with Mark Levison

    Mark Levison recently wrote a blog on “Scrum Alone is Not Enough”, which is the first blog of a series to uncover various Agile patterns. Till now he has published blogs on Kanban Portfolio View and Portfolio Management in the series.

  • Coding Culture: How To Build Better Products by Building Stronger Teams

    Software developers spend a tremendous amount of time and energy focused on how to build the best possible products. We obsess over what web framework to use or whether to go with a NoSQL or SQL database. While these questions are important, they often neglect to address an equally important aspect of software development: culture.

BT