Valentin Tudor Mocanu described upgraded form of pair programming using pairing and non-solo development.
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.
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.
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.
Daniel Schauenberg described at QCon London how Etsy, renowned for its DevOps and Continuous Delivery practices, does 50 deploys/day. A fully automated deployment pipeline, thorough application monitoring and IRC-based collaboration are all important to achieve this rate of change while keeping risk to a minimum. Etsy has about 60 million monthly visits and 1.5 billion page views per month.
At the recent DevOps Days in New York, Kevin Behr, co-author of “The Visible Ops Handbook” and ”The Phoenix Project”, and Jesse Palmer gave a talk on how they instilled a continuous improvement culture into an operations team. InfoQ interviewed Kevin Behr to know more about the approach that was taken.
When enterprises implement agile ways of working, questions can arise if changes are needed in the way performance appraisals are being done? Several authors have suggestions on how you can use feedback next or as a replacement for existing appraisal processes, to improve the performance of individuals and teams.
Collaboration between agile team members, like developers and testers, helps to make teams successful. What can scrum masters do to help testers and developers to work together in agile teams, and improve collaboration?
The Appsecute platform aims to improve collaboration and increase productivity through consolidating information associated to an applications lifecycle. The software as a service platform accepts messages directly from people and from integrated technology platforms, then it aggregates those events online for viewing by everyone within an organization.
A Gartner research report from December 2009 predicted that by 2012 “agile development methods will be utilized in 80% of all software development projects”. Let's check if the prediction from Gartner has come true?
Scrum and Pomodoro are blended by Mangus Nord to maximize both team and individual productivity.
Andrew Montalenti on his blog pixelmoneky.org talks about viability of fully distributed teams now and in the future.
Design thinking is about creating vision of the future, not just managing the present. Bill Burnett from Stanford University recently spoke about design thinking and what questions we need to ask to shift from design to design thinking.
Mike Cohn recently suggested that the Daily Standup (or Scrum) is not a status meeting for the Scrum Master, but a forum where team members are synchronising their work. Techniques such as breaking eye contact are helpful for Scrum Masters to fix this anti pattern in their teams.
For years Agile has been encouraging teams to work together collaboratively in open spaces and encouraging developers to pair program, but lately these types of practices have been coming under fire.