BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Roles Content on InfoQ

  • Slack Details Its New Role Management Architecture

    Slack recently posted a detailed description of the software architecture of its new role management system. Slack needed to build a system that was more flexible than the one it previously had. It created a custom containerized Go-based permission service that integrates with its existing systems over gRPC. As a result, its customers' admins now have granular control over what their users can do.

  • Product Owner Is a Bad Bad Idea

    The question of whether the product owner role is good or not clearly depends on a lot of factors, including team maturity, organisational maturity, organisational type, organisational complexity, and the product owner themselves. Some thought leaders are challenging the function of the role especially in these VUCA (volatile, uncertain, complex, ambiguous) times.

  • Azure Role-based Access Control Reaches General Availability

    In October, 2015 Microsoft announced its Azure Role Based Access Control (RBAC) feature has reached General Availability. The purpose of this feature is to allow organizations finer granularity when providing individuals and groups access to Azure resources and services.

  • Challenges When Implementing Microservices and Why Programming Style Matters

    Fred George talked about the Challenges in Implementing MicroServices and The Secret Assumption of Agile at the GOTO Amsterdam 2015 conference. InfoQ interviewed him about how make microservices as small as possible, challenges when implementing microservices and how to deal with them, why programming style matters, and what developers can do to develop their code writing skills.

  • Scrum Masters with the Imposter Syndrome

    Geoff Watts, talks about the Imposter Syndrome of Scrum Masters. Impostor syndrome is a psychological phenomenon in which people are unable to internalize their accomplishments.

  • The Role of the PMO in an Agile Organization

    This post describes the changed role of PMO (Project Management Office) in the Agile organizations.

  • The Need for a Product Champion

    Ron Jeffries recently posted about the need for a Product Champion, someone who knows the customer marketplace, who can be accountable for maximizing success. He discusses how in many Scrum, XP and "Agile" teams the Product Owner is not adequate for the task and that by taking the perspective of a Product Champion they can deliver great outcomes.

  • The State of Testing in 2015

    The state of testing survey 2015 aims to provide insight in the adoption of test techniques and practices, test automation, and the challenges that testers are facing. Ongoing developments have impact on testing, such as the Internet of Things (IoT) and the adoption of agile where developers and testers collaborate in teams and competencies become more important than roles and titles.

  • Is Getting Rid of All Projects a Good Idea?

    At the XP Days Benelux conference, Paul Kuijten did a session called "kill all projects" where he questioned if getting rid of all projects could be a good idea. InfoQ did an interview with Paul about project management practices that can be valuable for agile, and the funding of product development.

  • Using Lessons Learned as a Dungeon Master on Roleplaying and Games in Agile Coaching

    Guillaume Duquesnay uses his experience with games and roleplaying in his work as an agile coach. At the Agile Tour Brussels he talked about leadership, facilitation and management styles where no authority was involved. InfoQ interviewed Guillaume on his coaching, facilitation and leadership skills, and asked him if playing games gives happiness and fun to people, and make them more productive?

  • Product Owner Patterns

    The Product Owner role is regularly debated and discussed. The challenges of the role and the responsabilities encompased by it are a frequent source of discussion and advice. Recently there has been discussion about common aspects of the role and the important activities a product owner needs to ensure happen on an agile project, and the difference between the product owner and product manager

  • 10 Suggestions for the Architect of an Agile Team

    Tom Hollander, a Solutions Architect at Microsoft Australia, held a presentation entitled The Role of an Architect in an Agile Team at TechEd Australia where he discussed what he does as an architect leading an agile team.

  • Do We Need an "Agile Team Lead" Role?

    Patrick Wilson-Welsh, Chris Beale, Gary Baker, John Huston, Daryl Kulak, and others are attempting to popularize the idea of a new role, the "Agile Team Lead", to supplant many of the existing leadership roles found in and around agile teams.

  • Presentation: Making Roles Explicit

    In this presentation recorded during QCon London 2008, Udi Dahan, The Software Simplist as he calls himself, explains why sometimes it is not enough to apply good OOP and patterns lessons. He introduces a new principle: make roles explicit.

  • Mapping Traditional Software Development Roles to Scrum

    Mapping traditional software development roles to just the three roles in Scrum can be challenging. Mike Cottmeyer attempts to provide an effective mapping which would help the teams.

BT