Agile 101 - Agile Artifacts - Project Management
This article gives you brief introduction about Agile Artifacts.
An artifact is one of many kinds of tangible by-products produced during the development of software. Project progress should be visible and measurable in order to be useful. Agile artifacts provide both strategic and tactical direction to the team as well as radiate project progress to the organization. 1. Product Backlog: - The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. - The Product Backlog is never complete, it only lays out the known and best understood requirements. - The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in the future releases. - As product is used and gains value, feedback is provided and the Backlog becomes larger. -Requirements never stop changing. Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog. 2. Sprint Backlog: - The Sprint Backlog is a subset of the Product Backlog that the team pulls into the sprint to work on. It is essentially the list of “To Do’s” a development team might be working during the current sprint. - The work items in the Sprint Backlog are broken down further into tasks by the team. - All items on the Sprint Backlog should be developed, tested, documented and integrated to fulfil the commitment. 3. Increment: - Each Sprint the development team produces potentially shippable product increment. - This product increment must align to the development team’s “Definition of Done” and this increment must be acceptable by the Product Owner. 4. Product Vision Statement: - It’s a quick summary, to communicate how your product supports the company’s or organization’s strategies. - The vision statement must articulate the goals for the product. 5. Product roadmap: - The product roadmap is a high-level view of the product requirements needed to achieve the product vision. - It also enables a project team to outline a general timeframe for when you will develop and release those requirements. - The product roadmap is a first cut and high-level view of the product backlog. 6. Product backlog: - The full list of what is in the scope for your project, ordered by priority. After you have your first requirement, you have a product backlog. 7. Release plan: - A high-level timetable for the release of working software. 8. Sprint backlog: - The goal, user stories, and tasks associated with the current sprint. 9. Increment: - The working product functionality, demonstrated to stakeholders at the end of the sprint, which is potentially shippable to the customer.