InfoQ Homepage Project Management Content on InfoQ
-
Applying Use Cases in Agile: Use Case 2.0, Slicing and Laminating
To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.
-
Documentation in Agile: How Much and When to Write It?
The Manifesto for Agile Software Development values "working software over comprehensive documentation". This core value asks us to think about how much and which kinds of documents are needed and when they need to be written.
-
Upcoming Book by Gojko Adzic on Improving User Stories
Would better user stories improve software delivery? Gojko Adzic thinks applying small changes to the way teams manage their user stories can have a huge impact on the actual outcomes of their software delivery. He announced that he wants to write a book about improving user stories if at least 5000 people show that they are interested by pre-registering themselves in January.
-
Behaviour-Driven Development: Value through Collaboration
The goal of a software project is to deliver value to stakeholders and Behaviour-Driven Development, (BDD), is designed for that, Viktor Farcic, a software developer working on transitions from waterfall to agile processes, states in the first of four blog posts describing his view on BDD.
-
How Can You Learn Early and Fast?
Agile suggest that teams should fail-fast to enable quick learning from mistakes. Learning from failure is one approach, you can also learn early and fast from successes, by doing experimentation, or by using a plan for knowledge acquisition.
-
Balancing Demand and Capability with Kanban
Kanban helps organizations to get insight into their work-in-progress, and establish a pull system where demand and capability can be balanced. A first step is to find out what the real capability is and visualize the flow. InfoQ interviewed Florian Eisenberg about evolutionary change and how you can balance demand and capability in organizations.
-
Rocket to Mars: A Sprint Planning Game
“Many team and their product owners believe that the team's unique job is to deliver more and more story points, but we consider this to be a complete misunderstanding of the relation between the team and the product owner” said Damien Thouvenin and Pierrick Revol. They ran a sprint planning game on investing time to produce stories, investigate issues, reduce technical debt, or do training.
-
Is Getting Rid of All Projects a Good Idea?
At the XP Days Benelux conference, Paul Kuijten did a session called "kill all projects" where he questioned if getting rid of all projects could be a good idea. InfoQ did an interview with Paul about project management practices that can be valuable for agile, and the funding of product development.
-
How to Scale the Product Owner Role
The product owner role from Scrum is used to interface between the business and development. In larger organization with complex products and many decisions that need to be made, having this role filled in by one person is often not feasible. InfoQ did an interview with Timo Punkka about the role of the product owner, lean portfolio management, and customer collaboration.
-
Practices for Scaling Agile in Enterprises
Enterprises that are adopting agile organizational-wide will at some time have to scale their agile practices. In a session at the Agile Methods in the Finance Sector and Complex Environment conference, attendees shared their experiences with scaling agile in enterprises.
-
Causes of UK Agile Mega-Project Failure Examined
A UK National Audit Office report and a leaked Universal Credit Programme internal survey blame the programme's failures on poor leadership and practices. The Universal Credit Programme being developed under the Department for Work and Pensions, integrates the benefit payments for millions of UK claimants. It was mandated to use Agile methods, however the implementation has been flawed.
-
Reduce Waste by Changing from Waterfall to Agile
Organizations adopt agile to be able to handle changes. Agile helps teams to deliver products that satisfy the needs of customers; products which do not contain unneeded (and unused) features. Lean software development says: everything not adding value to the customer is considered to be waste. How can a transition from waterfall to agile software development help organizations to reduce waste?
-
Benefits of Combining Agile and Lean Startup
Enterprises want to increase their capability to deliver value to customers in less time. Many adopt agile software development to iteratively develop and deliver software solutions. Lean startup aims to support developing new businesses and products. Several authors shared their views on how combining agile and lean startup methods can be beneficial.
-
Latest Technology Trends on the Radar
Thoughtworks recently released a new installment of their technology radar highlighting techniques enabling infrastructure as code, perimeterless enterprises, applying proven practices to areas without, and lightweight analytics.
-
How Individuals Can Adopt an Agile Way of Working
Organization mostly do an agile transformation for a whole team, project, or organizational unit, given that agile is a team driven approach. But there are also professionals who start using agile practices individually, or who are working agile as a one person team. How can individuals adopt agile, and what kind of benefits can it give them?