Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Within XP, are there any specification baselines, test baselines, QA Acceptance testing, and CM Release Management/Change Control?

0
Posted

Within XP, are there any specification baselines, test baselines, QA Acceptance testing, and CM Release Management/Change Control?

0

XP is an inherently incremental process, with software being released to “production” as frequently as possible. This generally means that programmers release their work to the common development pool approximately daily, and that means that if a full system were built on that day, their code would be included in that build. The time period between full system builds varies depending on the environment: since you have chosen a particularly difficult integration language (C++), I could imagine that you would build less frequently. We would recommend, however, that the full system be integrated as often as possible, at least daily. (This may seem aggressive to you. We’d have to talk about what is possible in your environment.) Since XP is incremental, developers are working in short time increments we call iterations: we recommend about three weeks. Features (user stories) are broken down to the point of detail that allows a developer and his partner to implement the stories they’re work

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123