Pair Programming is good for increasing the software quality and collaboration within team members but it is hard to implement. This news describes the reasons why it is hard and how to figure out good practices of pair programming for your team.
When people work together in agile teams, emotions are bound to happen. Where positive emotions can give a boost to team working, negative emotions can have significant impact on collaboration in teams and affect their productivity. Noel Radley published a report on how team mood can impact project management. InfoQ asked her why negative emotions happen and how agile teams can deal with them.
At the Dare Festival Antwerp 2014 Jurgen Appelo talked about his new book Management 3.0 Workout and showed examples how organizations can improve the way that they manage themselves.
JetBrains has made available Upsource 1.0, a source code collaboration tool for software development teams.
InfoQ is researching the factors that influence the mood of teams. As team mood is an aggregation of the individual moods of team members, understanding the individual mood and how it influences team working can help to learn more about team moods. InfoQ interviewed Gerald Weinberg about individual and team mood, influencing the mood of individuals and discussing moods in teams.
Software development initiatives include different types of meetings, spread across the whole development process. A post on the Mobile Orchard blog explains tips and tricks to check and improve the effectiveness of these meetings.
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.