The Prioritised Requirements List (PRL) is baselined during the Foundations phase. This phase is critical for establishing a clear understanding of the requirements and priorities before the development work begins.
Baselining the PRL ensures that there is a formal agreement on the scope and priorities of the requirements, which serves as a foundation for subsequent development iterations.
References:
* Business Analysis.pdf, "requirements validation is carried out to review and agree the requirements documentation...At this point the CIs that describe the requirements are said to be 'baselined'".

The lifecycle of a Requirement in an Agile project includes the stages of Elicitation, Analysis, and Management and documentation. Elicitation involves gathering requirements from stakeholders. Analysis is the process of understanding, refining, and prioritizing these requirements. Management and documentation involve maintaining requirements and ensuring they are properly documented and tracked throughout the project lifecycle.
References:
* Business Analysis.pdf, "requirements elicitation 189-93, requirements analysis 185-6, requirements management 218-22".

A good User Story should include Acceptance Criteria. Acceptance Criteria define the conditions that must be met for the story to be considered complete and ensure that the developed feature meets the user's needs and expectations. These criteria provide a clear and measurable way to verify that the functionality works as intended and helps in achieving a shared understanding between the development team and the stakeholders.
References:
* Business Analysis.pdf, "The user story will generally be framed to answer the questions Who? What?
Why?...and include acceptance criteria".

When defining and planning a larger workshop, it is crucial for the Workshop Owner, with the support of the Workshop Facilitator, to ensure that all participants have enough information to make effective decisions. This involves thorough preparation, including distributing necessary documents and context ahead of the workshop, setting clear objectives, and ensuring that all participants understand their roles and the workshop's goals. This careful preparation helps to facilitate effective decision-making and productive discussions, leading to better outcomes from the workshop.
References:Business Analysis.pdf, Chapter 5, Investigation Techniques

Delivering a horizontal slice of the solution during iterative development allows for a high-level end-to-end prototype of the solution to be demonstrated. This approach provides an overview of how different components of the system interact with each other and helps in identifying any integration issues early. It offers a comprehensive view of the entire system, which can be valuable for getting early feedback from stakeholders and ensuring that the overall architecture is sound before diving into detailed development.
References:
* Business Analysis.pdf, "horizontal traceability concerns tracing the requirement from inception to delivery".