In the book series the art of managing remote teams authors share their experiences and provide advice on establishing and working with remote teams. The books are intended for people who are about to setup an offshore or nearshore team, or people who are already managing a remote team and want to improve.
Valentin Tudor Mocanu described upgraded form of pair programming using pairing and non-solo development.
In agile projects the product owner is often seen as the person who primary assures the connection between business and IT. But for effective IT-Business alignment having a product owner is not enough. What can people from the business, demand and supply parts of the organization do increase the effectiveness of IT – Business alignment?
The State of Testing 2013 report contains the results of a survey done by Joel Montvelisky from PractiTest together with Tea-Time with Testers. The survey, which has been filled in by people from testing and QA communities, provides insight in the adoption of test techniques and practices, test automation, and the challenges that testers are facing.
Teams can become so focused that they forget the world around them and risk losing contact with stakeholders. This makes it difficult for them to know what their customers need and how end users will use their products. At the ASAS2014 conference Daisy Rasing-de Joode will show how successful agile teams create synergy by being interdependent and highly collaborative with their environment.
Long working days, deadlines and team pressure can impact the quality of the software that agile teams deliver. What can we do to prevent that from happening and enable teams to improve the quality of their software? Some suggestions are to arrange for scope and deadline slack, adopt pull systems, and to make sure that people can slow down and get enough sleep.
Agile retrospectives are mostly done at the team level or at a project level. What if you need to conduct a retrospective with 50 teams or more? Luke Hohmann describes how a large scale agile transformation project did a huge retrospective to create insight on what was going well and what needed to be improved.
Blameless post-mortems of production incidents are increasingly seen as an essential fixture of any organisation's procedures. Mathias Meyer, from Travis CI, shared how blameless post-mortems had a profound effect on him. InfoQ took this opportunity to have a look at post-mortem practices of organizations like Etsy, GitHub or Chef.
The Guide to Critical Success Factors in Agile Delivery discusses the values, benefits and challenges of agile and proposes critical success factors for implementing an agile delivery in the federal government. InfoQ interviewed Paul Gorans about implementing agile practices, how agile impacts acquisition and procurement, scaling agile communication and the usage of reviews in agile.
Top-down implementation of agile is a commonly use approach for agile adoption in organizations. Alternative approaches exist, like implementing agile by stealth, using continuous improvement teams, starting with a quiet phase or taking baby steps by implementing a limited set of agile practices.
As the need for software products and services increases organizations look for ways to increase their capacity. Often organizations decide to scale up by adding more people. Some question this approach and suggest alternative ways to be able to deliver more software without adding people.
At DevOpsDays Amsterdam, Mark Coleman asserted that all organizational's cultural changes start with one person influencing another. He finds that Charles Handy's writings on power and influence help on understanding how an organizations works and how one can go on to change it. Mark discussed Charles Handy's six sources of power and six methods of influence.
Roman Pichler shared his views on product owner’s participation in sprint retrospective to increase collaboration with development team.
On the first day of DevOpsDays Amsterdam 2014, bol.com, an online store, reported its experiences in its DevOps journey. Full automation, careful team building and an agile mindset that cross-cuts the organisation were the keys to success. RunDeck, Puppet, Hiera and Nagios enable bol.com to build and monitor a full working environment in under two hours, in a fully automated fashion.
In organizations that are adopting agile people sometimes state that the hierarchy should be abolished and that we should get rid of managers. They consider managers and hierarchy to be something that hinder self-organization of teams.