Page History

...

§6: We plan with the following sprints (as per Releases):

• Sprint E release dev sprint 1: Aug-23 to Sep-12 (as per Releases)

• Sprint E release dev sprint 2: Sep-13 to Oct-3

• Sprint E release dev sprint 3: Oct-4 to Oct-24

• Sprint E release dev sprint 3: Oct-25 to Nov-14 (last planned development sprint)

• Sprint E release dev sprint 5: Nov-15 to Dec-3 (only for unplanned last-minute development items)

• Sprint F release dev sprint J release dev sprint 1: Feb-21 19 to Mar-13 (as per Releases)10
• Sprint F J release dev sprint 2: Mar-14 11 to AprMar-331
• Sprint F J release dev sprint 3: Apr-4 1 to Apr-2421
• Sprint F J release dev sprint 4: Apr-25 22 to May-15 12 (last planned development sprint)
• Sprint F J release dev sprint 5: May-16 13 to Jun-5 2 (only for unplanned last-minute development items)
• Sprint G I release dev sprint 1: Aug-22 21 to Sep-1110
• Sprint G I release dev sprint 2: Sep-12 11 to Oct-21
• Sprint G I release dev sprint 3: Oct-3 2 to Oct-2322
• Sprint G I release dev sprint 4: Oct-24 23 to Nov-13 12 (last planned development sprint)
• Sprint G I release dev sprint 5: Nov-14 13 to Dec-4 3 (only for unplanned last-minute development items)

§7: Some useful direct links to Jira:

1. Filter All RICP items: E release only
   1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-s, subteam-a and all teams.
      
   2. committed items only: all teams (committed)
2. Filter All RICP items: F release only
   1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-s, subteam-utfpr, subteam-p and all teams.
      
   2. committed items only: all teams (committed)
   3. items that are known to require work, but are currently not in F release: link
3. Filter All RICP items: G release only
   1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-s, subteam-utfpr, subteam-p, subteam-c and all teams.
   2. committed items only: all teams (committed)
   3. items that are known to require work, but are currently not in G release: link
4. Filter All RICP items: H release only
   1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-c, subteam-ag, subteam-cg 
      
   2. committed items only: all teams (committed) and all teams (committed + tentative).
      
   3. items that are known to require work, but are currently not in H release: link
5. Filter All RICP items: I release only
   1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
      
   2. committed items only: all teams (committed) and all teams (committed + tentative).
      
   3. items that are known to require work, but are currently not in I release: link
6. Filter All RICP items: J release only
   1. committed (90% sure) and tentative (90...30% sure) items: subteam-n (Nokia), subteam-h (HCL) , subteam-p (Parallel Wireless) , subteam-s (Samsung), subteam-utfpr (University UTFPR), subteam-ag (Abhijit Gadgil), subteam-cg (CapGemini, subteam-r (Rakuten), subteam-gs (gslab.com)
      
   2. committed items only: all teams (committed) and all teams (committed + tentative).
      
   3. items that are known to require work, but are currently not in J release: link
7. Filter: All RICP items that are not yet done: all = epics only + non-epics.
8. Test Epic and test user story Use RICP test epic RIC-42 and the linked test user story RIC-43 to experiment with JIRA. Right now these are mapped to team/board for team T1: board #16 .
9. All Epics (not only RICP): link
10. Search for a word in any of the RICP items: link

...