InfoQ Homepage Collaboration Content on InfoQ
-
Prototyping an Organization to Improve the Way of Working
Can you use evidence-based practices to test, validate & improve the way of working in an organization. Jo Martens from Nascom talked about prototyping your organization at the Dare Festival Antwerp 2014. He presented how they use experiments with evidence to do organizational change.
-
Deploying Transparency and Self Regulating Management to Get Actions Done
At the Lean Kanban France 2014 conference Bjarte Bogsnes gave a keynote presentation about beyond budgeting. In his presentation he talked about the problems with traditional management and how transparency and self regulating management comes to the rescue, and the principles and practices of beyond budgeting.
-
Designing Systems for Testability
Testability must be explicitly designed in the system said Peter Zimmerer from Siemens AG. Test architects should drive testability and collaborate with architects, designers and testers in using good design and engineering practices. At the QA&Test 2014 conference Peter gave a tutorial about design for testability for embedded software systems.
-
Different Approaches to Create Story Wall
Ryan Mckergow explains various ways to set up story walls for agile team. This post includes setting up columns, rows, selecting colors and avatars for the story wall.
-
Effectiveness of Meetings in Development Process
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.
-
The Importance of Discipline in Agile
Agile software development is sometimes perceived as an undisciplined way of working. There are organizations which use that perception as an excuse to not adopt agile. According to others agile is actually a more disciplined approach than waterfall for software development. Let’s explore how discipline plays a role in agile and why discipline is considered important for agile to be successful.
-
Cooperative Development Using Pair Programming and Non-Solo Development
Valentin Tudor Mocanu described upgraded form of pair programming using pairing and non-solo development.
-
How Agile Can Yield Effective IT Business Alignment
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?
-
Blameless Post-Mortems
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.
-
Delivering More Software Without Adding People
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.
-
On Power and Influence
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.
-
Active Participation of Product Owners in Sprint Retrospective
Roman Pichler shared his views on product owner’s participation in sprint retrospective to increase collaboration with development team.
-
Bol.com's DevOps Journey
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.
-
Q&A with Bob Marshall about the Antimatter Principle
Software development can be viewed as collaborative knowledge work. Such a view calls for different ways to manage organizations and the people who work in it. Bob Marshall wrote several blog posts about the antimatter principle. InfoQ interviewed him about this principle and the practices to use it to attend to the needs of people.
-
Replacing Orchestration by Autonomy to Speed Up the Software Delivery Cycle
Software delivery in a modern company requires autonomy to make releasing software easy. Niek Bartholomeus gave the presentation orchestration in meatspace at the DevOps Summit in Amsterdam where he discussed how can we change enterprises from orchestration to a more autonomous approach, in order to speed up the feedback cycle from idea to production.