PRODUCT GOALS: Create branch and model for Product Goals

[CarsonF]

Waiting on @sethmcknight for input on the product's new steps list

[sethmcknight]

Steps for Written Approach:

1. Exegesis & First Draft
2. Team Check
3. Community Testing
4. Back Translation
5. Consultant Check
6. Completed (need a text field or list to select from to define completed)

[sethmcknight]

Steps for Oral Translation Approach:

1. Internalization & Drafting
2. Peer Revision
3. Community Testing
4. Back Translation
5. Consultant Check
6. Consistency Check & Final Edits
7. Completed (need a text field or list to select from to define completed)

[sethmcknight]

Steps for Oral Storytelling Approach:

1. Craft
2. Test
3. Check
4. Record
5. Completed (need a text field or list to select from to define completed)

[sethmcknight]

Steps for Sign Language Methodology:

1. First Draft & Team Check
2. Exegetical Checking
3. Community Testing
4. Reviewing
5. Consultant Check
6. Completed (need a text field or list to select from to define completed)

[sethmcknight]

All of the other Products will be a single step that we will track a % complete for.

[sethmcknight]

@CarsonF Here are the steps as I know of them today. Some of the wording may change but this should get you started with the model.

[CarsonF]

It looks like these steps are a progress reporting metric. So the users will never enter which steps they are picking for the product. But instead they'll say they are this far in the "pipeline". I.e. 4 out of 5 steps done.

I remember seeing that progress percents needed to be captured by quarter. Is that truly necessary or can we just maintain a history and show when the percentages change?

[sethmcknight]

It looks like these steps are a progress reporting metric. So the users will never enter which steps they are picking for the product. But instead they'll say they are this far in the "pipeline". I.e. 4 out of 5 steps done.

The steps are both a planning and a progress reporting item. For a given project we may plan to Complete the book of Luke, Consultant Check the book of Acts and only Draft the book of Romans.

Users then track their progress in each step. (ideally the actual verses but in the interim just a %)

I remember seeing that progress percents needed to be captured by quarter. Is that truly necessary or can we just maintain a history and show when the percentages change?

I'm open to discussing how we capture that data in the DB. What we need to keep in mind is that (1) we do not currently require progress to be updated more than once/quarter and (2) the progress information is often reported after-the-fact, so users are reporting when the progress happened regardless of when it's being reported.

[CarsonF]

Parent issue #1737

[CarsonF]

@sethmcknight for Completed what additional info is needed from user?

[CarsonF]

Each step has its own progress info?

[CarsonF]

At least one step is required right?

[sethmcknight]

@sethmcknight for Completed what additional info is needed from user?

For planning we need a definition of complete. I think we can get that down to a pre-defined list for each Approach.

For we'll also need to capture progress % like we are for the other steps.

[CarsonF]

product-progress branch pushed.