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.
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.
Our efforts to improve software development face the question what to focus on. We can’t be predictable if we are not adaptable. What we really need is to be predictably adaptable.
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.
Iterative development requires gradual flow of small-sized, prioritized requirements from end customers to delivery teams. The use of all-conclusive, rigid, non-negotiable BRDs leads to dysfunction
Iterative development requires gradual flow of small-sized, prioritized requirements from end customers to delivery teams. The use of all-conclusive, rigid, non-negotiable BRDs leads to dysfunction.
The story of how Medtronic Neuromodulation realized that in order to modernize their processes while maintaining compliance, adopting integrated Application Lifecycle Management was necessary
The book Diving For Hidden Treasures 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.
It can be difficult to change from a Waterfall approach to the Agile practice in which requirements are prepared ‘just in time. The secret to success in Agile is ruthless management of scope.
This article explores how Fujitsu UK applied SEMAT and Essence to systems engineering, to combining agile and traditional methods and look at the whole programme of work across all disciplines.
There are dozens of Agile methods nowadays and more and more often we hear about Hybrid Agile, but what does that mean? The author presents some thoughts on what Hybrid Agile actually means. 2
InfoQ interviewed Dave Snowden about applying leadership models, the Cynefin model and how it can be used for capturing requirements, scaling agile, and sustainable change.
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
PMI's new Business Analysis Certification (PMI-PBA)® Domains
This article is a compilation of a series of published blog posts, found on Converging 360, written by Barbara Carkenord throughout the writing of the publication PMI-PBA® Exam Prep Guide.
The New PMI-PBA® Designation
As the world’s leading association for project management professionals, PMI monitors their members’ interests, successes and challenges.
PM eLearning From Anywhere
Live Virtual Training From Anywhere