InfoQ Homepage Project Management Content on InfoQ
-
/articles/kanban-scaling-agile-ultimate/en/smallimage/logo-agile.jpg)
Ultimate Kanban: Scaling Agile without Frameworks at Ultimate Software
Ultimate Software settled on Kanban as its scaled methodology which went hand-in-hand with the company’s culture of autonomy. Teams define their own process and apply policies specific to their own context. Through the innovative use of flow practices and principles, Ultimate has been able to achieve many of the benefits of a Lean-Agile implementation without the use of a heavyweight framework.
-
/articles/agile2016-visibility-devops/en/smallimage/GettyImages-170955949.jpg)
Dennis Ehle on Visibility into the DevOps Value Chain
At the recent Agile 2016 conference, InfoQ spoke to Dennis Ehle about the evolution of DevOps and the importance of having visibility into how value is delivered over the DevOps pipeline.
-
/articles/designing-the-requirements-an-alternative-approach/en/smallimage/image001.jpg)
Q&A with the Author on "Designing the Requirements”, an Alternative Approach
In the book “Designing the Requirements: Building Applications that the User Wants and Needs”, the author Chris Britton proposes an alternative path that goes from understanding the requirements to deliver spot on solutions.
-
/articles/standardize-requirements-scrum/en/smallimage/logo-agile.jpg)
Standardizing Requirements Descriptions on Scrum Projects for Better Development and Testing Quality
Standardizing requirements descriptions on Scrum projects benefit development and testing quality. Without standardizing, the project may suffer. Standardizing requirements descriptions provides a minimum of eight benefits from requirements descriptions unification, which in turn positively affects testing and makes management of ongoing changes in requirements easier with the help of tools.
-
/articles/book-review-liftoff-second-edition/en/smallimage/logo.jpg)
Q&A and Book Review on Liftoff, Second Edition
The book Liftoff, Second Edition by Diana Larsen and Ainsley Nies, provides practices and insights for chartering teams by understanding their needs, building trust, and defining how they will interact in the team and align with other parts of the organization. It's a book for Agile coaches, Scrum masters or agile product and project managers to help teams to understand the why behind the work.
-
/articles/predictably-adaptable/en/smallimage/dimitar-logo.jpg)
Adaptable or Predictable? Strive for Both – Be Predictably Adaptable!
Our efforts to improve software development face the question of what to focus on. Should we govern for predictability without concern of value, maximizing cost-efficiency without concern for end-to-end responsiveness? Or maybe do the opposite and govern for value over predictability, focus on responsiveness over cost efficiency? What we really need is to be predictably adaptable.
-
/articles/virtual-panel-bimodal-IT/en/smallimage/logo.jpg)
Virtual Panel on Bimodal IT
Bimodal IT has been supported by many and criticized by many. InfoQ reached out to enterprise experts to dig deeper into the pros and cons of this strategy and how/when/if is it applicable.
-
/articles/wtf-requirements-agile/en/smallimage/logo-agile.jpg)
WTF requirements in Agile Product Development
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
-
/articles/waterfall-requirements-agile/en/smallimage/logo-agile.jpg)
Waterfall Requirements in Agile Product Development
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
-
/articles/alm-safety-critical/en/smallimage/iStock_82671183_MEDIUM.jpg)
Why ALM Is Becoming Indispensable in Safety-Critical Product Development
Integrated Application Lifecycle Management platforms are advancing product development in life and safety critical environments. The story of how Medtronic Neuromodulation were able to modernize their processes using ALM helps us understand current and future trends in the development of complex software-heavy products.
-
/articles/book-review-cost-of-delay/en/smallimage/book-cover.jpg)
Q&A with Johanna Rothman and Jutta Eckstein on Cost of Delay
The book Diving For Hidden Treasures - Uncovering the Cost of Delay in Your Project Portfolio by Johanna Rothman and Jutta Eckstein explores how projects become delayed and provides tools and methods to analyze and limit the costs of delay in projects.
-
/articles/user-stories-placeholders-requirements/en/smallimage/agile-logo.jpg)
User Stories Are Placeholders for Requirements
It can be difficult to change from a Waterfall approach where ‘business analysts write big requirements up front’ to the Agile practice in which requirements are prepared ‘just in time’, and are the responsibility of the entire team. The secret to success in Agile is ruthless management of scope.