BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Content on InfoQ

  • The Day I Became Unnecessary - Part 2

    In the second of two articles Claudio Kerber talks about his experiences in team formation and collaboration and explains the process whereby he "became unnecessary" as the team he was working with built trust and cohesion through trust, shared knowledge and shared experiences. He examines the theoretical underpinnings and discusses ways in which servant leadership emerges.

  • Commitment – Writing a Graphic Novel explaining Real Options

    Building on their work on Real Options, Chris Matts and Olav Maassen are writing a graphic novel to explain the concepts and share their knowledge in the area. They discussed the novel, the process of producing it and the crowdsourcing model of funding with Shane Hastie from InfoQ. A sample chapter is available for InfoQ readers to download.

  • The Day I Became Unnecessary - Part 1

    In the first of two articles Claudio Kerber talks about his experiences in team formation and collaboration and how empowerment, refinement and facilitation enable the free flow of knowledge and value across team members and how cohesion emerges in collaborative teams.

  • The Need to Focus on App Delivery Lifecycle in PaaS

    An App Delivery Platform-as-a-Service is not only a development platform. It is also a social platform, a deployment platform, and a user engagement platform. An App Delivery Platform-asa-Service is all about delivering apps that perfectly fit the business, it’s about creating business value, it’s about enabling the business to be successful!

  • Communicate Business Value to Your Stakeholders

    Often project leaders—even Agile project leaders—talk about their projects in terms of features. Yes, and what do features really mean for stakeholders? Features are what your system or process can do. Benefits are why people care. And benefits equal business value. Learn why and how to communicate benefits rather than features—and what it will mean for you, your team and your organization.

  • Agile Development Team Charter

    Project Charters have rightfully focused on scope & goals for the project. However, team members can be unclear on their roles, activities, and expectations. This is especially true for people new to Agile. The Agile Development Team Charter addresses this gap by reviewing the Agile Prime Directive, Incremental Innovation Statements, and Team Member User Stories to provide clarity and context.

  • Faster, Better, Higher – But How?

    One of the main challenges when designing software architecture is the consideration of quality attributes. Not only their design turns out to be difficult, but also the specification of these attributes. Consequently, many problems in software systems are directly related to the specification and design of quality attributes such as modifiability or performance, to name just a few.

  • 10 tips on how to prevent business value risk

    One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor. The authors provide insight into the underlying causes of business value risk and provide ten tips on how to avoid them.

  • Your Brain on Scrum

    Status, Certainty, Autonomy, Relatedness, and Fairness are wired into the human brain. Michael de la Maza how the latest neuroscience findings support agile software development and that there are good brain-based reasons why agile is so effective.

  • New Book: Agile Software Engineering with Visual Studio

    “Agile Software Engineering with Visual Studio – from Concept to Continuous Feedback” is a new book that provides a deep-dive into the Visual Studio-TFS features, that can help Agile teams manage their application lifecycle better. It is written by Sam Guckenheimer (Product Owner, Visual Studio Strategy at Microsoft) and Neno Loje (Independent ALM Consultant and TFS specialist).

  • Dialogue Sheets: A new tool for retrospectives

    Dialogue sheets allow teams to hold facilitator-less retrospectives. They promote self-organization and encourage everyone to speak in the exercise. This results in great levels of participation in and higher energy levels in teams. The sheet itself is A1 in size, 8 times larger than a regular sheet, pre printed with instructions and questions to motivation discussion.

  • The Rise of Application Analytics: A New Game Demands New Rules

    When developers know how their applications are really being used “in the wild,” they will build better software, more efficiently, and with greater confidence. Sebastian Holst shows you how using application analytics.

BT