/
[BD-05] ORA v3: Usability + Moderation

[BD-05] ORA v3: Usability + Moderation

 

Blended Project ID

BD-05

edX Product Lead

@Marco Morales (Deactivated)

edX Technical Primary

@Justin Lapierre (Deactivated)

Provider

OpenCraft

Provider Lead

@Giovanni Cimolin da Silva

Calendly Scheduling Link

Slack Channel

#ora-dev,

Meeting Cadence / Preference

Scheduled bi-weekly project team syncs

Action Item Tracking

Use slack first, can also add action items on project status pages or provider status page

Escalation Path

https://openedx.atlassian.net/wiki/spaces/COMM/pages/1529676506 Escalation path outlined here

Relevant Discovery Documents

Discovery doc

Status Update Frequency

Bi-Weekly

Blended Project Epic (Tracks pull requests)

BLENDED-91

Target Completion Date

TBD 2020

~Dev Hours Per Sprint Expected

27 hours this sprint

Total Hours Used

88% - 2/8

Open Action Items

Status Updates

Time Frame

Updates & Actions

~Hours

Time Frame

Updates & Actions

~Hours

June 15 - June 29

Work done this sprint:

  • TNL-7273 Change ORA Report Download to use Usernames instead of anonymous IDs

Ongoing work from this sprint:

  • TNL-7274 Add a Grade Status Summary Message

  • TNL-7272 Separate “Assessment Steps” and “Schedule” from Settings Tab

New work for next sprint:

  • TNL-7282 Support Flexible Peer Grading Averaging for Learners delayed / in Peer Grading step (Postponed due to LSE tickets pushed in)

  • TNL-7281 Change ORA Report to Include Problem Name and Location

I've also looked at React integration points for both LMS and Studio, and, as discussed in the meeting, I'll send an email following up on that.

How is the budget coming along?
We've used 75.3 hours of the 331 hour budget.

From these, around 5 hours were used to onboard developers in the project.

 

22.7% - 6/29

June 29 - July 13

Work done this sprint:

  • TNL-7281 Change ORA Report to Include Problem Name and Location

Ongoing work from this sprint:

  • TNL-7274 Add a Grade Status Summary Message

  • TNL-7272 Separate “Assessment Steps” and “Schedule” from Settings Tab

New work for next sprint:

  • TNL-7282 Support Flexible Peer Grading Averaging for Learners delayed / in Peer Grading step

  • TNL-7308 Add ORA Zipped File Download for Submission Text + Attached Files

  • TNL-7311 Rewrite Open Responses Dashboard in React

  • TNL-7310 Discovery: pluggable ORA Submission Editor

We've used 105.8 hours of the the 331 hour budget.

32% - 7/13

July 13 - July 27

Tasks from last sprint waiting for edX review:

  • BB-2504 ORA v3 - Add a Grade Status Summary Message

Tasks from current sprint still in progress:

  • BB-2502 ORA v3 - Separate “Assessment Steps” and “Schedule” from Settings Tab

    • This is almost done and should be ready for edX review soon.

  • BB-2505 ORA v3 - Rewrite Open Responses Dashboard in React

  •  BB-2620 ORA v3 - Discovery: pluggable ORA Submission Editor

New tasks:

  • BB-2651 ORA v3 - Add ORA Zipped File Download for Submission Text + Attached Files

  • BB-2621 ORA v3 - Support Flexible Peer Grading Averaging for Learners delayed / in Peer Grading step Story

  • BB-2731 ORA v3 - Rewrite Studio block selector using React

  • BB-2732 ORA v3 - Make peer dependent steps skipable 

We've used 118.8 hours of the the 331 hour budget.

Some work from last sprint was postponed because of pending LSE tasks, so we’re ramping up the capacity on this epic in this sprint.

July 27 - August 10

Tasks from last sprint waiting for edX review:

  • BB-2502 ORA v3 - Separate “Assessment Steps” and “Schedule” from Settings Tab

    • This is almost done and should be ready for edX review soon.

  • BB-2505 ORA v3 - Rewrite Open Responses Dashboard in React

    • Paused

  • BB-2651 ORA v3 - Add ORA Zipped File Download for Submission Text + Attached Files

  •  BB-2620 ORA v3 - Discovery: pluggable ORA Submission Editor

Tasks in progress:

  • BB-2621 ORA v3 - Support Flexible Peer Grading Averaging for Learners delayed / in Peer Grading step Story

New tasks:

As per @Marco Morales (Deactivated)'s request, we’re pausing this epic for 1 to 2 sprints until the TNL and OpenCraft team have more availability.

This pause will allow both teams to work on less projects at the same time.

We've used 184.3 hours of the the 321 hour budget.

August 10 - August 24

Tasks waiting for edX review:

  • BB-2502 ORA v3 - Separate “Assessment Steps” and “Schedule” from Settings Tab

  • BB-2651 ORA v3 - Add ORA Zipped File Download for Submission Text + Attached Files

  •  BB-2620 ORA v3 - Discovery: pluggable ORA Submission Editor

New tasks:

As per @Marco Morales (Deactivated)'s request, we’re pausing this epic for 1 to 2 sprints until the TNL and OpenCraft team have more availability.

This pause will allow both teams to work on less projects at the same time.

We've used 207 hours of the the 321 hour budget (we might recoup some hours after next sprint).

September 21 - October 5

What's left to do? (Is it on track to be done before the deadline and within the hours budget?)

  1. Studio changes: No need to rewrite block selector into React component, just implement functionality in Backbone and the current mechanisms. 

  2. Pluggable editor: blocked on upstream.

  3. LMS Instructor dashboard rework: build new MFE.

New tasks:

Following sprint:

Tasks in progress:

Tasks waiting for upstream review:

We've used 262.4 hours of the the 321 hour budget.

October 5 - October 19

New tasks:

Following sprint:

  • Add integration of from LMS to new MFE

  • Update documentation

Tasks in progress:

Tasks blocked on edX:

Tasks waiting for upstream review:

We've used 301.7 hours of the the 321 hour budget.

October 20 - November 2

@Marco Morales (Deactivated) Doing some adjustments to the budget:

  • Total hours spent: 321h

  • Hours spent by newcomers above the estimates: 69h - we’ll absorb these hours.

  • Underestimated tasks - time difference: 10h

  • Scope changes/injections: 51h

    • 23h of work done related to React embedding, approach changed and now we’ll use an MFE

    • 12h to set up MFE

    • 12h ORA conversion to pluggable app

Considering those:

  1. The total amount of project hours used is 321h - 69h = 252h.

  2. We’ll need to add 61h to the current budget to finish all items in the project.

New tasks: no new tasks, all tasks are now blocked and waiting for reviews.

Tasks in progress:

Tasks blocked on edX:

  • https://openedx.atlassian.net/browse/TNL-7573

    • Instructor dashboard v2 (in MFE)

    • Student grade override views (in MFE)

    • UX dependency on this work as well

  • Implement pluggable ORA Submission Editor

  • Add integration of from LMS to new MFE

  • Update documentation

Tasks waiting for upstream review:

We've used 252 hours of the the 321 hour budget.

See note in the Update about budget calculation change.

November 2 - November 16

New tasks:

Tasks blocked on edX:

  • https://openedx.atlassian.net/browse/TNL-7573 - ready for review

    • Instructor dashboard v2 (in MFE)

    • Student grade override views (in MFE)

    • UX dependency on this work as well

    • Add integration of from LMS to new MFE

  • Implement pluggable ORA Submission Editor

Waiting:

Tasks waiting for upstream review:

We've used 270 hours of the the 321 + 61 hour budget.

December 14 - December 29

There’s a 2 sprint gap of updates here, this update will cover all items done in the last two sprints, as well as work planned for the next sprints and blockers.

Tasks completed and deployed to production:

Tickets done that unblock work:

Tickets in the current sprint & next sprint (until Jan 10):

Starting in the current sprint, as @Justin Lapierre (Deactivated) and @Mat Carter (Deactivated) request, we’ll use the EDUCATOR board to track tickets and work.

Pending discussions:

  • MFE API architecture? How to build ORA (mix of XBlock and Django app) APIs for new MFE and ESG?

    • Discussion started by @Ben Warzeski (Deactivated) on Slack, continuing on public channel and ticket

    • Decision here impacts the work being done on the MFE

New work scope (needs budget evaluation, estimates coming):

We've used 290 hours of the the 382 hour budget.

December 29 - January 11

?

 

January 11 - January 25

?

 

January 25 - February 8

I was on vacation and the two previous entries were not written. I’ll include a recap of tasks done and budget status on this update.

Tasks ready for edX review:

Tasks in progress:

Next sprints:

https://openedx.atlassian.net/browse/EDUCATOR-5363 will unblock us to implement the remaining work in the ORA repo.

We've used 339 hours of the the 382 + 20 hour budget.

The extra 20 hours came from a scope increase discussed in the last two meetings. See the notes and it’s comments below to get the full context.

Note: Other tracking docs have 416 hours as max budget, calculation for now to be based on that max for now. (339/416: 81.4% - 1/29)

February 8 - February 22

Waiting edX review:

Blocked waiting on requirements:

Done:

  •  Read discovery and test React based views on Xblock

Next sprint: 

  • Implement instructor dashboard waiting step - 8h timebox for sprint 240

Tickets left:

  • Update documentation



We've used 359 hours of the the 406 hour budget.

February 22 - March 8

Waiting edX review:

Done:

Next sprint: 

Tickets left:

  • Update documentation

We've used 372 hours of the the 406 hour budget.

Meeting Notes

Date

Attendees

Agenda

Notes, decisions and action items

Date

Attendees

Agenda

Notes, decisions and action items

2020-02-04

@Giovanni Cimolin da Silva @Marco Morales (Deactivated) @Sapana Thomas (Deactivated) @Justin Lapierre (Deactivated)

Status update

  • @Giovanni Cimolin da Silva Presented a demo of the ORA pluggable submission editor (simple editor, tinymce and codemirror)

    • Public sandbox linked on ticket

    • Ready for edX’s technical and product review.

  • make sass → webpack conversion in internal review, should land soon

  • Waiting on edX product requirements for ZIP file

  • Work unblocked on instructor dashboard: a react integration is now possible and the waiting step details will be delivered within the next two sprints

  • Documentation tasks: we’ll hold off on those until we finish all the implementation tickets, to reduce the ticket overhead and unecessary budget usage.