reskinning of website in sprint

I don't have many answers, mostly questions:



1- Why are you reskinning the website? Is there any reason why this could not orient the Sprint Goal? If the goal is too ambitious, is there any way you could scope it down for a first sprint (and potentially do more in the following sprint)? For example, could a partial reskin that the team believes is achievable in one sprint deliver some value?



2- Is the issue that your current definition of done doesn't apply to this kind of work? You could consider adapting it, as long as the product owner and development team agree.



3- Why not? Is your team unable to make any releasable change whatsoever to the website in a sprint, or are you trying to do the entire reskin in one release?



You could try thinking of it differently: Your website's look and feel has to change and it's the number one priority for now, but we're only giving the team one sprint's duration to work on it. The product owner has to figure out what's most important in the reskin, and the team has to figure out how much of it they can do.

> 1- how can we decide sprint goal?

Isn't the Sprint Goal to improve the website's look-and-feel?

> 2- how can we fetch the item for sprint with the definition of done?

Why wouldn't the team be able to decide what "Done" should mean for this work?

> 3- it seems that we can not create potentially releasable product Increment in this case

Why not? Why wouldn't it be releasable?

Ok I will try to elaborate

Example: our team needs to reskin the whole website of approx 100 pages, and it is not possible to complete this website in one sprint of 1 month.

for this case, development team picks the backlog item for first spring for 15 days sprint.

Q- what would be the sprint goal? 

Is it correct to have sprint goal like 'Reskin the website of 10 pages.' 

if above example is correct for, it is not a potentially releasable product at the end of the sprint.

we can not release the website with mix theme/skin.

do you think waterfall model is best in this case?

Here is my suggestion on this:

1. In your case Sprint Goal should be more like 'Reskin the website for a section e.g. Apparel section in case of e-commerce website'. The reason why 10 or some other number shouldn't be included in sprint goal as it doesn't allow dev team to renegotiate the scope if required.

2. Definition of done means it is potentially releasable. So, I am sure in doing reskin you must have a criteria which if met then the the increment is showed as Done.

3. Potentially releasable doesn't mean that the whole thing should be released to the market. It means that the done increment is ready(coded, tested, documented etc.) and whenever it suits the most, it can be delivered to the client/market.

Are there any significant risks or complexities in this reskinning exercise which would justify an agile and emergent approach?

If it won't fit in one Sprint, it sounds like a large piece of work which may benefit from empirical control.