Product increment. Let's talk about these Scrum art department. So what we see on this illustration, we see a box and we see a check mark. And normally check mark symbol assumption stable Thomsen functional Thomsen well done. And that's true while the product increment, or whirl product increment represents a result of the work done in the sprint. Well, let's talk about as a major characteristic as a product increment.

So product increment is a prescribed Scrum artifact. Or in other words, it's mandatory for the scrum product, the increment should always appear after the first sprint. So even if you're speaking about brand new team, we should still consider that you're in the first sprint brand new team should prepare something functional, something valuable to the business, or in other words, a piece of functional work in software. And finally, product increment must be potential. Ready for the release, as the core wart here is potential uranium. Let's look involved true statements regarding their product increment.

Its drusen product owner and drive as a business and decide to introduce the release of the increment. So product owner for whatever reason may decide to do release and for whatever reason may postpone the release and it's up to the product owner to decide when to release and that's absolutely correct. Let's review the full statement regarding the product increment. It's false statement that product increment should be shipped upon the end of every sprint. So this statement is not correct. And the tricky thing here is that we are speaking about shipping.

So whenever speaking about shipping, we consider that this is going to be deployed into production environment and available to the customer and of course That's not the Amanda directivity we already covered that product owner should decide whether it should be shipping or not. And there is also being difference between be ready for shipping and actual ship Sampson. So what development teams should do is they should have a product increment in good state or good enough state and conditions that will allow them to deploy it or ship it, if it will be needed, of course, but it's not mandatory to ship it. So it's a big difference. Now let's talk about other artifacts which are non prescribed artifacts but still used in Scrum. Well, let's talk about them.