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 Most Common Reasons Why Software Projects Fail

    Knowing the basics of software development can greatly improve the project outcome; however, that alone is not enough to prevent project failures. Projects can be categorized as failures because of cost overruns, late deliveries or poor quality, but the right estimation processes can increase the likelihood of project success.

  • The World is One Family - Why That Matters for Software Corporations and Professionals

    Rev. C. L. Gulati of Sant Nirankari Mission presented the opening keynote on the conference theme – Vasudhaiva Kutumbakam – The World is one family, at the Regional Scrum Gathering South Asia 2015. Kamlesh Ravlani, one of the volunteer event organizers, spoke with him about this philosophy, its implications for global organizations and why the software community should care about it.

  • Practices for DevOps and Continuous Delivery

    DevOps is an attempt to break the barrier between development and operations teams, who are both required for the successful delivery of software says Danilo Sato. His book Devops in Practice: Reliable and automated software delivery provides a hands-on approach for implementing continuous delivery and DevOps practices.

  • Business, Design, and Engineering: Developing Collaboration-Culture

    The collaboration of a company and its multidisciplinary units has never been more crucial than now. Everything we make today depends upon our ability to stay current, move nimbly, innovate, engage and delight. Those things are too difficult to achieve without cross-team collaboration.

  • Implementing Agile Delivery for Non-Software IT Projects

    Most organizations avoid using Agile for IT projects that do not involve software delivery (e.g. roadmap planning and architecture development). These projects deliver high value, but are often the most risky of all projects - and high risk demands Agile delivery. This paper discusses how Agile can be successfully adopted to deliver these projects by going back to the basics of Agile philosophy.

  • Lessons Learned Adopting Microservices at Gilt, Hailo and nearForm

    This article contains an extensive interview on the microservices adoption process, the technologies used, the benefits and difficulties of implementing microservices, with representatives from Gilt, Hailo and nearForm.

  • Q&A with Ron Jeffries on The Nature of Software Development.

    The book "the nature of software development" intents to help people to organize their thoughts about value and find ways to deliver value in software development. It's a book of questions, not of answers, says author Ron Jeffries, for readers to discover the natural way to develop software, the simple way, inside themselves.

  • Business, Design and Technology: Joining Forces for a Truly Competitive Advantage

    The list of industries being disrupted by digital technologies is growing. To embrace this new digital world, companies need to change their practices and the way they use technology.

  • User Story Driven Docs

    At OutSystems we stopped trying to document the UI and started doing user story driven documentation. In this article I'll tell you why you should avoid document the UI, and how to check if you're already doing it. I'll also tell you how focusing on user stories changed our team's culture, and the process we're currently using to create documentation for OutSystems Platform.

  • From a Project to a Product Approach Using LeSS at Agfa Healthcare

    By changing the inner workings from a project perspective to a product perspective Agfa Healthcare established a less complicated process using a single backlog for the entire organisation. Main advice is to try to avoid setting up silos where they do not belong. When applying LeSS it is important to stick to its basic rules even though they are, in most organisations, very disruptive.

  • An Agile Input Management Process Framework - The Agile IMP

    Agile methods and processes such as Scrum give us conceptual tools to implement our innovative ideas. But that toolset seems to miss a crucial part: A well-structured ideas development process. The Agile IMP (Input Management Process) proposes a conceptual framework for managing input from multiple sources, for maturing input and for basing product decisions on soundly evaluated propositions.

  • DevOps & Product Teams - Win or Fail?

    Peter Neumark found a new world when he moved from a DevOps infrastructure team to a Lean product team.How to experiment frequently while keeping operational performance? Platform teams to the rescue!

BT