Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Gantt chart, roadmap, and timeline ― three common concepts in project management. But what do these terms really mean?
If you’ve been wondering about the true meaning of these terms and their differences, you’re in the right place.
Maturity models are based on consistent, systematic, linear-scale assessments and representations of existing software delivery processes that are applied through standardized methods of evaluation. This enables maturity quantification of methods, ways of working, and applications of technology in the software delivery processes.
Maturity models are arguably good for organizations that seek consistent, measurable improvement. In those organizations, different areas of software development can be assessed and rated (e.g., defect management process maturity, test data management process maturity, etc.), and subsequently benchmarked against a standard or industry average.
The practice of capturing backlog items as user stories is well-established, to the point that many now consider them indispensable to an Agile way-of-working. In short, a user story is a placeholder for a conversation about a possible requirement. It isn’t so much a requirement specification as a vehicle through which a team can evolve a shared cognizance of scope. A user story can, therefore, be seen as a very practical construct. It allows for an emergent understanding of what the requirements actually are.
An Agile sub-culture has developed around these “stories” and the practices through which they are best managed. For example, user story mapping is a popular technique which has emerged as a discipline in its own right, and there are training courses on how to apply it. Other techniques present lower barriers to entry and usage and are effectively considered part and parcel of the user story lexicon. The most widely adopted of these is arguably the Epic.