AOrthVector
commented
3 years ago Adding Acceptance Criteria would be helpful to indicate what indicates completion of the work. For example, for the RDD example above, what verification would need to be done to verify the data has been loaded and loaded correctly?
SaPeresi
The Kanban board is set up with an Epic for the POC. We should be breaking this Epic into Stories of a functionality. The story should be in the format of
As a < type of user >, I want < some goal > so that < some reason >, the success of which is shown by < some verification >.
An example would be:
As a user of Kanplex, I want to create a job that will access a VA data file on z/OS using Jzos on USS, so than it will print all the records to the display to verify the read - number of records should be verified and data is the same. Another might be: As a developer in Jzos on USS, I want to take z/OS accessed records so that I can summarize the records and display the aggregated records to verify the summarization is working correctly, no records are dropped and summarization is accurate. and: As a user in USS, I want to create RDD files from z/OS files so that I can verify they have been loaded to spark tables, no records are dropped and data is accessible.