Hi All,
I came across a question, what would be the check list we should keep in mind after the user story has been completed before deploying the changes to the UAT and Prod?
As you know, always route your changes from DEV to UAT to PROD.
Cheers!
Having clear user stories makes it easier to get them approved. Investing time in reviewing user stories with the client before development begins will make your work much smoother.
In your user stories you should have this structure: As a [role], I want [functionality] so that [goal]. Example user story from the Level 3 training:
User Story 1.1 As a Regional Sales Executive, I need to use the FY20 monthly forecasted revenue by country and product family from the FP&A model to create a Baseline Financial Forecast in the Sales Planning model. The Baseline Financial Forecast from the Finance business unit will be a starting point for establishing the Initial Sales Targets.
I’ll know this is complete when I can review the quarterly Baseline Financial Forecast sales revenue data for each country by product family, for the current year (FY20).
I have 2 lists used in modelling, In Input module I'm using subset of territories from Country List and subset of Regions from Flat list. But in Output module,Its reversed, I'm using subset of regions from Country list and subset of territories from flat list.How to derive the numbers from input to output module. I do have…
This shows all comments across all data to all users with access to the UX page. This is not appropriate for any UX which might contain security access sensitive data. Comments on grids and cards ARE security dependent. That works fine. But anyone with access to the page can open this Summary Panel and see ALL comments…
If anyone is aware of idea exchange ideas that are currently being evaluated by the product team, if you don't mind linking them here, would love to give them an upvote. Thanks!