InfoQ Homepage Agile Content on InfoQ
-
Keeping Development ‘On Track’ with Use-Case Slices at Dutch Railways
How can you get from high level system requirements (features/epics) to the right level of specification to enable agile development? This article describes how Dutch Railways made the transition from large use cases which were completely written before development, to “Use Case 2.0” and why this helps them to deliver apps faster and with the right business value.
-
Self-service Delivery Platform at Tuenti
Óscar San José, technical lead at Tuenti (largest Spanish social network) explains how and why their in-house Flow deployment system allowed developer teams to be more independent and deliver faster.
-
Making a Difference: a Case Study of Change in the Public Sector
At Spark the Change 2015, Tracy Jelfs shared a case study of change in Children’s Services at Monmouthshire Council. Spark attracts the UK’s most innovative organisations, and this story impressed leaders from many different industries. It is a showcase of how radical change is possible even in difficult circumstances – from poor performance and low morale to a heavily regulated environment.
-
Downscaling SAFe
The Scaled Agile Framework (SAFe) with custom modifications to it in accordance with Agile and Lean values helped Seamless Payments to go through a period of organizational growth and prepare for further growth. This article describes the change that was done using a slimmed down version of SAFe that still maintained its core ideas.
-
Scrum Alone is Not Enough – An Interview with Mark Levison
Mark Levison recently wrote a blog on “Scrum Alone is Not Enough”, which is the first blog of a series to uncover various Agile patterns. Till now he has published blogs on Kanban Portfolio View and Portfolio Management in the series.
-
The Hierarchy of Needs
What may be valuable to customers whom you do not even know in an unstructured and completely individualized market? This article suggests prioritizing your backlog using an enhanced quality model based on Maslow’s hierarchy of human needs. Search for most valuable features using the Need-Feature-Capability matrix and give those features highest priority in your backlog.
-
A Case for Diversity in Our Workspaces
Dr. Sallyann Freudenberg makes a case for supporting neurodiveristy in our workplaces.
-
Increasing your Agility: An interview with Dave Thomas
At the GOTO Amsterdam 2015 conference Dave Thomas gave a keynote presentation titled "agile is dead". While the "Agile" industry is busy debasing the meaning of the word, the underlying values are still strong. Dave Thomas suggests to stop using the word agile and switch to agility: repeatedly taking small steps towards where you want to be and evaluate what happened.
-
7 Habits of Highly Effective Monitoring Infrastructures
There is a right way and a wrong way to engineer effective telemetry systems and there is a finite combination of practices which — whatever your choice of individual tools — are predictive of success. If you are building or designing your next monitoring system, take a look at this short list of habits exhibited by the most successful monitoring systems in the world today.
-
The Practice and Future of Release Engineering
This article features highlights from interviews with release engineers on the state of the practice and challenges in release engineering space. The interview questions cover topics like release engineering metrics, continuous delivery's benefits and limitations.
-
Book Review and Q&A on Agile IT Organization Design
Sriram Narayan’s book – Agile IT Organization Design, provides a basis for reviewing and reshaping the IT organization to equip it better for the digital age. The book covers how structural, political, operational, and cultural facets of the organization design influence overall IT agility.
-
Developing a High Capacity Network Gateway with LeSS
This report summarizes how the Large-Scale Scrum (LeSS) framework was used in developing a high capacity network gateway and how to grow R&D from 2 co-located teams to 20+ teams. It also describes how LeSS and agile development practices significantly accelerated the time to market and gave us the flexibility that traditional development practices never offered.