"A prioritized list of project requirements with estimated times to turn them into completed product functionality. Estimates are in days and are more precise the higher an item is in the Product Backlog priority. The list evolves, changing as business conditions or technology changes." (Ken Schwaber, "Agile Project Management with Scrum", 2004)
"A list of all to-do items for an application used in Scrum, corresponding to the OpenUP/Basic concept of a work item list." (Bruce MacIsaac & Per Kroll, "Agility and Discipline Made Easy: Practices from OpenUP and RUP", 2006)
"In Scrum, the list of features not yet implemented by the application." (Rod Stephens, "Beginning Software Engineering", 2015)
"An ordered list of user-centric requirements that a team maintains for a product." (Project Management Institute, "Practice Standard for Scheduling" 3rd Ed., 2019)
"A listing of product requirements and deliverables to be completed, written as stories, and prioritized by the business to manage and organize the project’s work." (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)
"A set of software features awaiting development in a subsequent iteration." (Project Management Institute, "Software Extension to the PMBOK Guide" 5th Ed., 2013)
"The number of open or unsolved incidents. It is a running count of the difference between new tickets and tickets resolved." (Darril Gibson, "Effective Help Desk Specialist Skills", 2014)
"In an agile approach, the backlog is the set of requirements to be implemented in the project." (Cate McCoy & James L Haner, "CAPM Certified Associate in Project Management Practice Exams", 2018)
No comments:
Post a Comment