I think the relative estimates in Ideal Person Days are the way to go. That allows us to size the User Stories based on the team's experience without getting bogged down in too much detail.
Hmm, I'm a bit confused on this one. I'm not sure if leveraging estimates from another team is the right approach, since the User Stories may be quite different.
I think the best approach here is to use relative estimates in Ideal Person Days, as that reflects the team's best collective judgment on the effort required.
Good point, Emogene. The Azure SQL Data Warehouse Connector seems like the most logical choice here to connect directly to the data source and leverage dataflows/recipes for the necessary transformations.
This is a tricky one, but I think the answer is two screens and one screen scheme. We can have one screen for both issue types during creation, and then a separate screen for Shoe Orders after creation to handle the Priority field requirement.
I'm a bit unsure on this one. The details about DNS and NFS access are throwing me off. I'll need to re-read the question and think it through step-by-step.
Tamekia
3 months agoBenedict
3 months agoColton
3 months agoErin
4 months agoCasie
4 months agoCoral
4 months agoKristeen
4 months agoShawn
4 months agoAriel
5 months agoFidelia
5 months agoCatina
5 months agoHildegarde
5 months agoLennie
5 months agoJustine
5 months agoGretchen
5 months agoStefania
5 months agoEmeline
5 months agoDaren
2 years agoEun
2 years agoKenneth
2 years agoJerilyn
2 years agoShonda
1 year agoKatina
1 year agoGladys
1 year agoGearldine
2 years agoTashia
2 years agoShawna
1 year agoJerrod
1 year agoBelen
1 year agoDorthy
1 year agoEmeline
2 years agoShizue
2 years agoLenna
2 years agoMyrtie
1 year agoDawne
1 year agoWilbert
2 years agoKati
2 years agoChi
2 years agoMarisha
2 years agoBarrett
2 years ago