In the coming years we will see less organizations, but not less organizing. Organizing is a daily activity to get things done, but we don't necessarily need organizations to do things. When individuals are subordinate to the organization, it's an inhibitor for adopting modern management approaches.
Sociocracy 3.0 is an open framework which supports collaboration in agile organizations and helps them to continuously improve products and services. The framework provides patterns for activities like coordinating work, effective meetings, governance, and building organizations.
At Craft Conference 2015 in Budapest, Mary Poppendieck discussed the ‘new software development game’ and offered advice on how best to utilise containers, microservices and consumer-based contract tests to lower friction and limit risk within software systems.
The Fearless Journey game, designed by Deborah Hartmann Preuss, builds upon the patterns described in the book Fearless Change. It is a game that teams can play to learn how to address obstacles over which they have no authority. Martin Heider and Holger Koschek facilitated a workshop where they talked about using patterns in change and played the Fearless Journey game.
Niels Pflaeging, founder of the BetaCodex Network, did the opening talk organize for complexity - how to get life back into work on the second day of the Dare Festival Antwerp 2014. He explained how decentralizing organizations is paramount to increase their performance and agility.
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.
To become agile you might need to change the core values and beliefs of an organization. Applying value systems from spiral dynamics can help organizations to go from doing agile to being agile as Dajo Breddels showed in the path to agility at the XP Days Benelux 2014 conference.
Most organizations hire Agile coaches to carry out an organization wide Agile transformation. The intention is to have a lean and fit organization by the time coaches walk out of the building. However, it is very difficult to achieve transformation that improves the end-to-end delivery process and is sustainable if the transformation just begins at the team level.
Pair Programming continues to be one of the most debated and controversial practices of recent years. Most proponents don't falter in their praise of the benefits, but many of even these same people will admit they struggle to get pairing really going in their shops. Why? Obie Fernandez opinions 10 reasons why this might be so.
Allan Kelly sites an article from MIT's Sloan Management Review about why it is important to get a team's technical competence and ability improved before focusing on business-IT alignment. This, he claims, is one of the reasons Agile software development has been so successful. Allan's point indirectly touches on a recent community debate about successful, valuable, Agile adoption.
In this interview from QCon San Francisco 2008, Ian Robinson discusses REST vs. WS-*, REST contracts, WADL, how to approach company-wide SOA initiatives, how an SOA changes a company, SOA and Agile, tool support for REST, reuse and foreseeing client needs, versioning and the future of REST-based services in enterprise SOA development.
Recently InfoQ reported on Jim Shore's 'The Decline and Fall of Agile', which highlighted a trend for organizations to adopt "Agile" (in name) but fail to adopt what it means to be Agile (in practice). Community leaders such as Joshua Kerievsky, Martin Fowler, and Ron Jeffries have taken Shore's post a few steps further recently, posting their own thoughts on what's going on with this situation.
Many important challenges faced by a software architect for a large company have as much to do with the organization as technology. In a recent blog entry, Dan Greenblog drew parallels between the principals behind software architecture and effective organizational structures.
As organizations continue to grow their IT investments (bought, borrowed, or built) and concepts like Business Process Management and Service Oriented Architecture become more common, the role of Enterprise Architecture (EA) has become more common. Recently, several people in the EA community have spoken about its current state.
In this article Stefan Tilkov, innoQ SOA consultant and InfoQ SOA Community editor, introduces a potential set of roles for successful SOA Governance. He describes the individual roles as well as the tasks assigned to each independent of any tool, vendor, or technology.