InfoQ interviewed Jan van Moll about regulatory demands for software in healthcare, satisfying these demands with waterfall project or with a mix of waterfall and agile, and introducing agile in an R&D organization that needs to fulfill regulatory demands.
The io.js TC has voted to join the upcoming Node Foundation. The project will be named Node.js but it will be based on io.js’ repository.
Organization that are adopting agile often look for ways to establish self-organized teams where team members are able to take more responsibility. Agile software development teams could improve their decision making by using the consent principle and sociocratic procedures. Sociocratic governance structures can also be used to scale up agile principles to every level of the organization.
Agile suggest teams to self-organize their work. The questions arise what self-organization is and what organization can do to make it possible for teams to become self-organizing.
Organizations look for ways to increase their agility and becoming more adaptive and responsive. There a new wave of modern ways for managing organizations, supporting transparency and self-organization, taking off. LiquidO is an organizational governance model for arranging activities and decisions and giving credit, allowing everybody in an organization to take part in management activities.
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.
When organizations decide to scale agile they can be looking for agile ways to define strategies, manage direction and sustain alignment. Deploying and stay aligned, is today's challenge said Pierre Neis. At the Lean Kanban France 2014 conference Pierre showed how using Hoshin Kanri has helped global players in their lean agile transition.
Creating and maintaining a Quality Management System (QMS) can be difficult, certainly when organizations have multiple product lines where different regulations and standards are applicable. InfoQ interviewed Willem van den Biggelaar about the benefits of having a QMS, dealing with multiple regulations, assuring adherence, how a QMS can support agility and deploying a QMS in an agile way.
At the Agile Governance conference in Amsterdam Jan van Santbrink presented how architecture when used with an agile mindset can play a key role in governance. InfoQ interviewed Jan about why agile and architecture need to collaborate, how architecture can support agile decision taking and the benefits for development of doing architecture.
How can we manage and govern multiple agile teams? At the Agile Governance conference in Amsterdam Christoph Johann Stettina presented about agile governance and the role of management. He studied 14 large European organizations on how they apply agile project management methods in IT project portfolios.
Trust is a decision about your investment in the relation says Anko Tijman. Agile governance should be build upon trust. At the Agile Governance conference in Amsterdam Anko Tijman presented being in control through people. Governance is often based on analytical control using structures and models.
Andrew Craddock will give a talk at the Agile Governance conference May 13 in Amsterdam about properly governed Agile projects. InfoQ did an interview with him about what agile governance is and why you need to embed governance practices into your agile development process.
Agile software development or Scrum is not enough to make your enterprise truly deliver on the Agile promises, says Dave van Herpen. He suggests that IT service management should apply agile and lean practices combined with DevOps to improve collaboration throughout the entire enterprise.
Most large organizations have allowed their systems to evolve without good architecture and governance. The result is a "hair ball" of systems interfaces and dependencies which greatly increase complexity, risk and the cost of change. David Sprott describes how systems modernization should be a collaboration between business management and IT.
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.