SCRUM for new products

[Krzysztof Kołodziej]

Hi, im working as a product owner for 2 scrum teams. ( 4 in the company )  
since 1 year we working on large and complex project. The aim is to deliver the product build in new architecture based on micro services and other modern architecture solutions. We planing that the software will be used by business (go live) after 2 years. As the value will be delivered as e2e process  will be ready. 

So assuming the product is not used by users in production.   ( we need all *sales, back office, reports , data warehouse, payment’s  , roles a/ users management and a lot of more to diver product to  production and start delivering  value for company. 

What practices are the best in class for products where go live in planed after whole systems is done? 

how often do QA,

 how often relase   ?  
, how to set the dod ?

How to measure value for company ? 

Once you provide answer please highlight why is this right approach.

Thanks KK

[Daniel Ebers]

Hi @Krzysztof Kołodziej

looking at this a bit older question of yours and thinking about the internals of it (we've been tasked with more in-depth agile topics, also) I think there is no answer that would fit for every company.
From what I observed questions like "how often to do..." is individual to companies, if not even teams - it's real hard to recommend something, not even based on best practise without understanding how your teams and your company works.

Consulting an experienced coach, like Bill, said sounds reasonable to me.

More of a basic reading, I found Atlassian's Agile Coach to be very helpful, maybe some of the questions can be answered there - you could give it a try:

https://www.atlassian.com/agile

Regards,
Daniel

[Bill Sheboy]

Hi @Krzysztof Kołodziej 

You seem to be asking: how do we manage, build, deliver, and support value for our product?  Essentially, how do we do the entire value stream?

One starting point would be to recruit and hire knowledgeable and experienced product managers, project managers, software engineering leads, and people leaders at the team and company level.  Then, engage with them to determine next steps.

Kind regards,
Bill