A: User acceptance tests or sometimes just known as acceptance tests are ultimately accepted or not accepted by a subject matter expert (could be a stakeholder).
Depending on the requirement this could be for example be the product or business owner. Sometimes, acceptance testing is automated to provide efficiencies; this requires close coordination and collaboration by testing teams (QA) and the business stakeholders.
Q: What do you consider as a successfully finished release?
A: One that has been deployed and is running in production! Or, if we follow the XP (Extreme Programming) convention, “all requirements / user stories have acceptance tests that pass and are accepted by their respective stakeholders for a particular sprint or release.” If you are a Scrum team, your release should meet the criteria for your Definition of Done.
Q: Is the File Release system a front-end to Nexus? Seems like they are equivalent of -SNAPSHOT builds.
A: No, the FRS (TeamForge file release system) is for published, generally available builds, these are typically builds that stakeholders and the community in general, should have access too.
The Nexus artifact repo may also have GA builds however it will also include many development builds (SNAPSHOTS) that result from a continuous build process (CI).
PI Planning aims to bring together all the people doing the work and empower them to plan, estimate, innovate, and commit to work that aligns with the business’s high-level goals, vision, and strategy.
Silvia Davis, Sr. Product Marketing Manager at Digital.ai, tells her story of how a positive app experience led to the realization that proper data integration is essential to the entire application lifecycle.
Regardless of where you are on your digital transformation journey, we can help you achieve your strategic outcomes and accelerate value delivery with the right combination of technology, services, and training.