InfoQ Homepage Agile Content on InfoQ
-
Supporting Digital Leadership with Agile
Digitization can no longer be stopped; with customers who increasingly act digitally and mobile it is important to show digital leadership. IT is taking over traditional services and is leading the way for new digital connected products. An organization applied agile to change the way teams are funded and to establish teams of owners who take responsibility to put good products in the market.
-
How Technical Practices Support Evolutionary Architecture and Continuous Delivery
Technical practices of XP such as TDD, Refactoring, CI and Pair Programming support emergent design and enable evolving your architecture. The first practice you need for continuous delivery is CI, committing to mainline every day. Being able to write clean, well-factored, and well-tested modular code is the most important skill for developers.
-
Should Teams Decouple Cadences?
Recently a Twitter discussion took place about allowing teams to have multiple cadences, for instance by using a different rhythm for planning the work and for learning and improving. Decoupling cadences gives teams room to explore and learn what works best for them; it can lead to more adaptability and autonomy and better outcomes.
-
How Google Develops New Managers
Alex Langshur, host of Google Partners Podcasts, has launched the podcast Google HR secrets: identifying & developing great managers, interviewing Sarah Calderon, People Development at Google, on how Google selects, trains, and develops their managers.
-
Using Agile Principles with Scrum Studio to Increase Organizational Responsiveness
Using a change approach based on agile principles with Scrum Studio helped a Dutch pension and investment management company to become more responsive at structurally lower costs. The change team practiced what they preached by applying transparent and iterative change with similar characteristics as the intended end result. They established a culture where people are taking responsibility.
-
Post-Mortems Trends and Behaviors
Eric Siegler presented his findings at Velocity from analyzing data from 1000 post-mortems ran by 125 different organizations over a six month period. Main trends include the prevalence of blameless post-mortems; the fact that only 1 in 100 post-mortems refer to "human error"; and that analyzing the lifecycle of incidents can provide useful insights on weaknesses in the incident response process.
-
XebiaLabs Announce DevOps Intelligence Engine
XebiaLabs, the developers of Continuous Delivery and DevOps tooling XL Release and XL Deploy, has announced availability of the first release of XL Impact, a goal-based, data-driven recommendation and decision making tool for DevOps organisations. XebiaLabs claims this is the first tool of its kind and the capability is essential for organisations to prove DevOps performance improvements.
-
Comparing Product to Project Funding
An exploration of recent thinking around product vs project funding. We look at a number of recent articles reflecting views on a product-centric focus by ThoughtWorks' Sriram Narayan , Jeff Gothelf, author of Lean UX Author, and Leon Tranter.
-
Game Changing Beliefs for Knowledge Working Organizations
Game changing beliefs carry the strength of the strongest walls to shape our behavior. The beliefs we choose to take on in our professional work are a leverage point. They can help us to change the culture and behavior in organizations to increase agility.
-
GitHub Team Discussions Aim to Improve Collaboration
Announced at its last Universe conference, Team discussions aim to power processes like planning, analysis, design, and others directly from within GitHub.
-
Service-Oriented Development: Rafael Schloming Shares Lessons Learned with Building Microservice
At QCon San Francisco, Rafael Schloming presented “Service Oriented Development”, and argued that an organisation migrating to microservices must seek to break up their monolithic development processes in addition to attempting to break up the system architecture. Treating newly formed microservice teams as internal “spinoffs” provides boundaries and encourages self-sufficiency and autonomy.
-
Using Self-Selection to Create Teams
At one company, self-selection was applied to redistribute people over teams. It provided the opportunity for developers to get involved in strategic decisions and understand the needs of the business. Using self-selection, they learned that by giving people the power to take difficult and informed decisions, they will become motivated, no matter how tough the decision is.
-
Real-Time Collaboration Comes to Atom
At QCon San Francisco 2017, GitHub’s Nathan Sobo has unveiled Atom’s new real-time collaboration plugin, Teletype. Teletype aims to make it possible for two developers to code together with the same ease as coding alone.
-
Q&A with Ken Schwaber and Jeff Sutherland about Scrum Guide Updates
The Scrum guide has been updated to better reflect what Scrum is and clear up misconceptions. Scrum can be used for building software products, and it can be applied to many other areas outside of software as well. Scrum is a framework based on empiricism for continuous improvement. Having a potentially shippable product increment at least every sprint or more often is a key element of Scrum.
-
Game Changers for Organizations
We want to approach strategy using choices, direction, and iterative experiments, establish a growth mindset in organizations, and work towards a common purpose or goal with leaders and teams sharing the same values, principles, and mindset; these are some of the game changers for organizations to become more innovative, deliver faster and better, and have happier and more engaged employees.