BT

InfoQ Homepage Co-Located Teams Content on InfoQ

Articles

RSS Feed
  • Engineering Culture and Methods InfoQ Trends Report - January 2018

    At InfoQ we regularly revisit the topics we focus on based on the technology adoption curve. This article provides a view of the topics we see as being important to the community at the beginning of 2018. Some new topics have appeared since 2017 and there have been some significant shifts in what matters to individuals, teams and organisations over the last year.

  • Engineering Culture and Distributed Agile Teams

    Franzen and Pahuja explain how a distributed agile framework can help distributed teams create an engineering culture based on over a decade of experience, and share actionable practices that help you get your distributed engineering tools and practices in place. Topics covered are devops, team structure, microservices, pair programming, T-shaped engineers, continuous integration and deployment.

  • Teams and the Way They Work

    The terms “self-organised” and “cross functional” are often used to describe a team. What does this mean, and how will you recognise if your team has these features? Great teams work with the uniqueness of each person’s skills, experiences and outlook – forging the motivation to achieve a shared goal, within the constraints in which they operate.

  • Characteristics of a Great Scrum Team

    This article explores 'What makes a great Scrum team?' by offering detailed descriptions of the characteristics and skills needed in the Scrum roles of Product Owner, Scrum Master and Development Team.

  • Building Hybrid Teams

    As globalisation and offshoring take over the workplace, building agile teams becomes more challenging - thankfully, here’s your non-PC (but culturally sensitive) guide on creating an environment that will allow you and your organisation to “kick some agile butt” no matter who or where you are!

  • An interview with Matt Winn on JP Morgan’s Agile Transformation

    Matt Winn, from J.P. Morgan’s securities group, Singapore describes his own perspective of using Large-Scale Scrum to create significant change within a tier-one financial services firm.

  • How To Not Destroy your Agile Team with Metrics

    The agile community needs to change how it measures success. The ways that we gather metrics and the information we seek out of those metrics is actually getting in the way of what’s most important, making working software. Forcing individual metrics sometimes discourages team collaboration by focusing too intently on others. This can skew the thing we’re measuring, thus defeating the purpose.

  • Lessons From A DevOps Journey

    Matt Callanan has been pushing the boundaries of Agile software development for over six years and most recently he extended that journey to DevOps. He recently shared his experiences in a talk at the Agile Development Practices West conference entitled "Lessons From A DevOps Journey". InfoQ caught up with Matt prior to the conference to find out more about his experiences in DevOps.

  • Adopting Agile Development Practices: Using Patterns to Share our Experiences

    Agile adoption often proves challenging. Participants at a recent OpenSpace event focused on the dynamics of adoption rather than the structure that results from adoption. The resulting patterns are part of an effort to compile Agile adoption patterns answering: "What specific practices should I adopt?", "How can I adopt incrementally?" and "Where can I expect pitfalls?"

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.