InfoQ Homepage Communication Content on InfoQ

Articles

RSS Feed

Newer Older

Conversation Patterns for Software Professionals. Part 1

All too often we that the business people we deal with do not know what they want, in this first article in a series Michael presents some ideas on how to talk to them and how to explore their needs. In this article he discusses how to manage a conversation, explore the needs and clarify expectations.

Michał Bartyzel
on Nov 22, 2014
Q&A with Gojko Adzic on Fifty Quick Ideas to Improve Your User Stories

The book fifty quick ideas to improve your user stories aims to help people to write better user stories, supporting teams in iteratively delivering products that satisfy the needs of their customers. InfoQ interviewed Gojko Adzic about the format of his new book, when and when not to use user stories, the ideas that the book provides, organizing product backlogs and prioritizing user stories.

Ben Linders
on Nov 15, 2014
Measuring and Improving Software Development Productivity

The book Improving Software Development Productivity contains practices, models and case studies to quantitatively support adoption of agile software development. An interview with Randall Jensen about measuring and improving productivity, contribution of agile to productivity, benefits from pair programming and teams, knowledge retention in maintenance and commandments for communication.

Ben Linders
on Oct 31, 2014
Stories of Collaboration in Remote Teams

Lisette Sutherland and Elinor Slomba are collecting and sharing stories from people whose business models depend upon getting remote teams right. These stories showing how remote teams collaborate, bridge distance, build trust and get things done together will be described in the upcoming book Collaboration Superpowers: The Remote Field Guide.

Ben Linders
on Sep 01, 2014
What Is Leading Self-Organising Teams All About?

What exactly do we have to do to capitalise on self-organisation? How can we best support our teams? What special kind of leadership is needed? The third article from a series on Leading Self-Organising Teams covers what it means to lead a self-organising team.

Peter Hundermark Sigi Kaltenecker
on Aug 25, 2014
Culture is the True North - Scaling at Jimdo

A lot of the pain that large and medium-sized organizations are facing boils down to scaling. It is not difficult to have 5-10 people working together in one room. However, as your business becomes more successful and your hiring increases, you will start to see problems. At Jimdo, the approach to scaling relies on three major factors: culture, communication, and kaizen.

Arne Roock
on Apr 24, 2014
Q&A with Robert Pankowecki on his book Developers Oriented Project Management

Self-organized teams manage their work, the processes that they use and the way that they work together as a team and with their stakeholders. Robert Pankowecki is writing a book on Developers Oriented Project Management which aims to help programmers, product owners, project managers and agile company owners to improve their project management practices and move towards more flat organizations.

Ben Linders
on Apr 10, 2014
Solving the Gordian Knot of Chronic Overcommittment in Development Organizations

Why do we promise more than we can deliver? Why do we say yes when we are already too busy? Chronic Overcommitment is a pervasive problem in the IT industry. In this article we take a look at the behaviors that drive over commitment and the dynamics at play in your organization the make it a difficult problem to solve. Finally, we offer some advice to those who suffer from this affliction.

Morgan Ahlström Rolf Häsänen
on Feb 13, 2014
Intelligent Evolution: Making Change Work

Some 80% of all improvement and change programmes fail: they did not achieve the expected results, the investment in the change programme was greater than the value achieved, “improvements” were seen as mostly bureaucratic, or changes were abandoned soon after the implementation. Intelligent Evolution ensures long-term business success rather than short-term satisfaction of a standard or theory.

Peter Leeson
on Jan 13, 2014
I’d Rather Be Coding – Writing Things Down

For lots of reasons, most developers hate writing down anything that isn’t code. The Agile Manifesto deemphasizes documentation, but there are times on a project when a little documentation can go a long way. In this article, we will explore why collaboration over comprehensive documentation shouldn’t mean “NO” documentation – and when you should stop coding and start writing things down.

Nate McKie
on Dec 31, 2013
Virtual Panel: Specification by Example, Executable Specifications, Scenarios and Feature Injection

In the last couple of years terms like Specification by Example, Executable Specifications and Feature Injection have showed up quite frequently in the community, often in relation to Behaviour Driven Development (BDD) or tools like Cucumber or SpecFlow. InfoQ have talked to some of the leading experts in this domain about what these practices are and how they relate to BDD.

Jon Arild Tørresdal
on Nov 10, 2011
New book - Individuals and Interactions: An Agile Guide

Ken Howard and Barry Rogers have written a book that focuses on the first value from the Agile Manifesto. They provide advice, tools and techniques to help teams and individuals improve their communications and interpersonal interactions. The book presents a set of tools that work together more effectively. They provide guidelines for a workshop to put the techniques into practice.

Shane Hastie
on Jul 18, 2011

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles