BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Business Content on InfoQ

  • MLConf NYC 2014 Highlights

    The MLConf conference was going strong in NYC on April 11th and was a full day packed with talks around Machine Learning and Big Data, featuring speakers from many prominent companies.

  • How Composite C1 Found Success by Becoming Open Source

    In today’s environment it is difficult to offer commercial products, especially in highly competitive fields such as content management systems. Finding themselves being squeezed out of the market, Composite C1 found a way to thrive by releasing their core product under an open source license with cloud based hosting.

  • Author Q&A – The Lean Mindset by Tom and Mary Poppendieck

    The Lean Mindset is a collection of research results and case studies from companies applying lean in product development and delivery. A lean mindset according to Mary and Tom Poppendieck is about “developing the expertise to ask the right questions, solve the right problems, and do the right thing in the situation at hand”.

  • Interview with Jan de Baere about the Rise and Fall of an Agile Company

    What happens when a director of a consulting company decides to drastically change the culture? At the Agile Tour Brussels conference Jan de Baere presented the why and how of a company that adopted agile, the journey that they went through, and how it came to a sudden end. InfoQ interviewed him about the agile change approach, culture and trust, and the lessons learned from an agile journey.

  • Tracking Schedule Progress in Agile

    The challenge of knowing whether we are on track to deliver haunts projectmanagers and developmentmanagers at various levels as their organizations take on agile approaches to product and project development. Driving towards smaller work items and lower work in process brings the benefits of both better project risk management as well as more effective agile execution and learning.

  • Retrospectives Applied as “PROspectives"

    We can view situations in our work as opportunities from which to learn how to better handle similar situations in future, by looking back and asking “How will I deal with future situations like this to improve my results?” PROspectives help us to reflect more often, independently of acute, unexpected problems and without time pressure, to uncover ideas for future improvements.

  • The Subject and Discipline of Business Architecture

    This article defines the subject and discipline of Business Architecture. In contrast with other approaches, only business functionality and business information may be considered architectural entities that together form the subject of Business Architecture.The discipline of Business Architecture on the other hand is a description of the primary and secondary tasks of a Business Architect.

  • The Best Process Is No Process

    Bureaucracy often plagues large product development efforts. Just like technical debt slows down development, process debt slows down your business. Have you ever experienced 12,096,000% savings in time? Clarify strategy. Automate processes. Parallelize work. Collaborate intently. Did you know a hidden MS project default may be causing inflexibility? Eliminate process debt. Get to market faster

  • Interview with Simon Brown about Sustainable Competence

    Why are some teams successful while others are less than stellar? Can teams use processes to do their work? How can managers help teams to become better? And do we need incentives to improve the quality of software? InfoQ did an interview with Simon Brown about sustainable competence for continuous improvement, balancing people and processes, and software quality and architecture.

  • API Business Models: 20 Models in 20 Minutes

    How do you make money from APIs? In this keynote from the 2013 API Strategy Conference, John Musser, founder of ProgrammableWeb, reviews the different API business models that have been adopted by the worlds leading technology companies. John distills the variety of models down to four core categories and shows how API implementation aligns with different business strategies.

  • The Integration of Agile and the Project Management Office

    Agile and the Project Management Office (PMO) are no longer considered diametrically opposed phenomena. With an ever-changing business landscape, organizations are required to adopt more nimble approaches. In many cases, Agile is more suitable within the PMO than people think.

  • Much Ado About Commitment

    Great projects are generally the end result of commitment from three basic sets of actors: individual team members, teams and projects. With agile teams committing based on the needs of the business and their capabilities, and delivering against the commitment they make.

BT