Update valet-forecast-lab.md

azure_devops/valet-forecast-lab.md

@@ -12,11 +12,23 @@ In this lab we will use the `forecast` command to forecast potential GitHub Acti
 TBD
 
 ## Prepare for forecast
+Before we can run the forecast we need to answer a few questions so we can construct the correct command.
+1) What is the date we want to start forecasting from?  __2022-03-02. This should be a date that will give enough data to get a good understanding of the typical usage.__
+2) Where do we want to store the results? __./tmp/forecast_reports. This can be any valid path on the system, but for simplicity it is recommend to use a directory in the root of the codespace workspace.__ 
+
+Using these answers our command becomes:
+```
+gh valet forecast azure-devops --output-dir ./tmp/forecast_reports --start-date "2022-03-02" 
+```
 
 ## Perform a forecast
+Instead of using the command generated in the previous step.  We will instead use a different one that will `forecast` using data previously generated.  
+
+The reason for this is that it is very likely that the ADO project generated for the Valet labs does not have any pipelines that have ran and probably no runners available.  So rather than setting up runners and triggering pipelines we will instead use the `--source-file` option of the `forecast` command. If you would like you can try the command above, it will likely return "no jobs"
+
 
 ## Review forecast report
-  
+  
 ### Metric Definitions
 |  Name | Description |
 | ----- | ----------- |