Produced by Araxis Merge on 12/7/2017 6:26:45 PM Eastern Standard Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
# | Location | File | Last Modified |
---|---|---|---|
1 | OSCIF_CPEE_Sprint_1 and 2.zip\Build 4 Deliverables | Build 4 Plan CPE CCSE 1.0.docx | Thu Dec 7 15:13:22 2017 UTC |
2 | OSCIF_CPEE_Sprint_1 and 2.zip\Build 4 Deliverables | Build 4 Plan CPE CCSE 1.0.docx | Thu Dec 7 18:27:50 2017 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 3 | 1682 |
Changed | 1 | 2 |
Inserted | 0 | 0 |
Removed | 1 | 10 |
Whitespace | |
---|---|
Character case | Differences in character case are significant |
Line endings | Differences in line endings (CR and LF characters) are ignored |
CR/LF characters | Not shown in the comparison detail |
No regular expressions were active.
1 | Claims Pro cessing an d Eligibil ity (CP&E) | ||
2 | Teams 1, 2 , and 3 | ||
3 | Build 4 Pl an | ||
4 | |||
5 | |||
6 | |||
7 | Department of Vetera ns Affairs (VA) | ||
8 | Office of Informatio n and Tech nology (OI T) | ||
9 | October 20 17 | ||
10 | Version 0. 4 | ||
11 | Document V ersion His tory | ||
12 | Date | ||
13 | Version | ||
14 | Descriptio n | ||
15 | Author | ||
16 | 9/21/2017 | ||
17 | 0.1 | ||
18 | Initial Dr aft | ||
19 | Michael Sy nakiewicz | ||
20 | 9/28/2017 | ||
21 | 0.2 | ||
22 | Adjusted S print User Stories b ased on de pendencies | ||
23 | Michael Sy nakiewicz | ||
24 | 10/06/2017 | ||
25 | 0.3 | ||
26 | Added Spri nt 3 | ||
27 | Michael Sy nakiewicz | ||
28 | 10/11/2017 | ||
29 | 0.4 | ||
30 | Adjusted S print 2 an d 3 | ||
31 | Michael Sy nakiewicz | ||
32 | 10/12/2017 | ||
33 | 1.0 | ||
34 | Added Deve loper and adjusted S print Plan hours | ||
35 | Michael Sy nakiewicz | ||
36 | Note: The revision h istory cyc le begins once chang es or enha ncements a re request ed after t he documen t has been baselined . | ||
37 | |||
38 | Table of C ontents | ||
39 | 1.Build Ex ecution1 | ||
40 | 2.Scrum Te ams1 | ||
41 | 2.1.Veloci ty2 | ||
42 | 2.2.Capaci ty vs. Pla n2 | ||
43 | 2.3.Org Ch art2 | ||
44 | 3.Epics, S ub-Epics a nd User St ories3 | ||
45 | 4.User Sto ries/Backl og6 | ||
46 | CP&E Backl og6 | ||
47 | 5.Testing Responsibi lities6 | ||
48 | 6.Acceptan ce Criteri a6 | ||
49 | 7.Schedule 7 | ||
50 | 7.1.Build 4 Sprint 1 7 | ||
51 | 7.2.Build 4 Sprint 2 10 | ||
52 | 7.3.Build 4 Sprint 3 12 | ||
53 | 7.4.Sprint Ceremonie s14 | ||
54 | 7.5.Build 4 Planning 15 | ||
55 | 8.Dependen cies15 | ||
56 | 9.Risks & Issues15 | ||
57 | 9.1.Identi fied Risks 15 | ||
58 | 9.2.Identi fied Issue s15 | ||
59 | 10.Constra ints15 | ||
60 | 11.Definit ion of Don e16 | ||
61 | 11.1.Build 4 Deliver ables16 | ||
62 | |||
63 | Build Exec ution | ||
64 | This docum ent descri bes the Bu ild 4 Plan for the C laims Proc essing and Eligibili ty (CP&E) project. The Build runs from September 28, 2017 t hrough Dec ember 19, 2017 and i ncludes 6 sprints of approxima tely 2 wee ks each. During the build, sc rum teams will elabo rate, anal yze, progr am, valida te, test a nd build u ser storie s in suppo rt of the business o wner’s pri orities. The priori tization o f items in the backl og is capt ured in th e Rational product b acklog. | ||
65 | Sprint Tea ms work to gether in sprints to produce c ode that c an be deli vered to t he VA for VA Quality Assurance (QA) and User Accep tance Test ing (UAT). | ||
66 | Defects fo und during sprints w ill be eva luated imm ediately b y the scru m team. De fects that can be re solved wit hin the sp rint will be tasked and resolv ed; FTC wi ll call th ese “Bugs” . | ||
67 | Defects th at cannot be resolve d within t he sprint will be pl aced on th e Build Ba cklog to b e resolved based upo n the busi ness prior ities. The se defects will be e valuated b y the scru m team and estimates will be l isted in R ational an d then pri oritized a nd approve d by the b usiness. A t the end of the two weeks a b uild is cr eated and demonstrat ed. Storie s with Hig h and Very High defe cts will n ot be cons idered com plete and will not b e demonstr ated at th e end of a sprint. S tories wit hout defec ts and sto ries with Low or Med ium defect s will be demonstrat ed for acc eptance. | ||
68 | During the two-week sprint per iod, we ar e preparin g for buil ding and d emonstrati ng the pro duct. We h ave contin uous deplo yment jobs that help s us keep our builds , packagin g our fixe s and prom oting the code from one enviro nment to t he next. W e keep con trol of ou r versioni ng and con trol of ou r configur ations, in cluding pr eparing te st data fo r our test s and fixe s. | ||
69 | A retrospe ctive cere mony is us ed to revi ew and app rove the w ork produc t complete d during t he two wee ks. | ||
70 | Scrum Team s | ||
71 | FTC will a ccomplish sprint pla nning base d on the f ollowing v elocity an d capacity . | ||
72 | Velocity i s based up on the tea m average over previ ous sprint s and will adjust ba sed upon t hat averag e througho ut the bui ld. | ||
73 | Capacity i s determin ed by the team membe rs assigne d and thei r availabi lity durin g the spri nt to acco mplish tas ks. | ||
74 | Build 4 Ve locity to be complet ed during the Build 4 timebox: 203 Story Points. | ||
75 | |||
76 | |||
77 | |||
78 | Velocity | ||
79 | The follow ing table illustrate s the tota l number o f points c ompleted b y each tea m during S print 3 an d the aver age points per sprin t. The vel ocity from Build 3 i s used to plan for B uild 4. | ||
80 | Team | ||
81 | Build 3 Co mpleted Po ints | ||
82 | Average Pe r Sprint P oints | ||
83 | Team 1 | ||
84 | 68 | ||
85 | 35 | ||
86 | Team 2 | ||
87 | 58 | ||
88 | 35 | ||
89 | Team 3 | ||
90 | 47 | ||
91 | 30 | ||
92 | Capacity v s. Plan | ||
93 | The follow ing table represents the full team capac ity (in ho urs) vs. t he planned work per sprint/per team (in hours). L OE roles, such as Pr oject Mang er and Bus iness Anal yst, are s pread even ly per use r story. | ||
94 | Team | ||
95 | Sprint 1 | ||
96 | Sprint 2 | ||
97 | Sprint 3 | ||
98 | |||
99 | Capacity | ||
100 | Plan | ||
101 | Capacity | ||
102 | Plan | ||
103 | Capacity | ||
104 | Plan | ||
105 | 1 | ||
106 | 253 | ||
107 | 247 | ||
108 | 217 | ||
109 | 200 | ||
110 | 253 | ||
111 | 260 | ||
112 | 2 | ||
113 | 253 | ||
114 | 273 | ||
115 | 217 | ||
116 | 142 | ||
117 | 217 | ||
118 | 176 | ||
119 | 3 | ||
120 | 253 | ||
121 | 247 | ||
122 | 217 | ||
123 | 181 | ||
124 | 253 | ||
125 | 178 | ||
126 | Org Chart | ||
127 | Team 1 | ||
128 | Team 2 | ||
129 | Team 3 | ||
130 | Michael S. CP&E – Pr oduct Mana ger | ||
131 | Steve G. – Certified Scrum Mas ter (CSM) | ||
132 | Cheryl H. – Business Analyst | ||
133 | Bharati M. – Configu ration Man ager | ||
134 | Faith D. - Tester | ||
135 | Diane S. - Tester | ||
136 | Angel K. – Technical Analyst | ||
137 | Anthony F. – MUMPS D eveloper | ||
138 | Lloyd M. – MUMPS Dev eloper | ||
139 | James G. – MUMPS Dev eloper | ||
140 | Cindy S. – MUMPS Dev eloper | ||
141 | Dennis B. – MUMPS De veloper | ||
142 | Hayes M. – MUMPS Dev eloper | ||
143 | Larry G. – MUMPS Dev eloper | ||
144 | Kathryn L. – MUMPS D eveloper | ||
145 | Shavkat S. – MUMPS D eveloper | ||
146 | Jeff E. – MUMPS Dev eloper | ||
147 | |||
148 | Barry J. – MUMPS Dev eloper | ||
149 | Epics, Sub -Epics and User Stor ies | ||
150 | The follow ing table describes the epics, sub-epics and user stories th at will be addressed in Build 4. Sprin ts 1 and 2 User Stor ies have b een assign ed, and de tail for t he remaini ng Build 4 sprints w ill be pla nned as pa rt of spri nt plannin g for each sprint. U ser Storie s are curr ently bein g defined and elabor ated accor ding to th e table be low. | ||
151 | Epic | ||
152 | Story# | ||
153 | Rational | ||
154 | Descriptio n | ||
155 | 005 | ||
156 | Epic 005 | ||
157 | RM: 720630 | ||
158 | As the Hea lth Claims Reimburse ment group , I want t o reopen E DI claims in the Cac he system so that I can proces s reopened EDI claim s in the C ache syste m. (CR ENC 005415). | ||
159 | 005 | ||
160 | 005-001 | ||
161 | RM: 883572 | ||
162 | As the Hea lth Claims Reimburse ment Group I would l ike to add a Program Indicator to the PD I to tell the system to ReOpen EDI. | ||
163 | 005 | ||
164 | 005-022 | ||
165 | RM: 902774 | ||
166 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the VE Productiv ity Summar y Report. | ||
167 | 005 | ||
168 | 005-023 | ||
169 | RM: 902210 | ||
170 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the Da ily Hourly Processin g Report. | ||
171 | 005 | ||
172 | 005-23a | ||
173 | RM: 938146 | ||
174 | As the Hea lth Claims Reimburse ment Group I would l ike a new menu optio n on the D aily Hourl y Processi ng Report to display EDI RO in formation in the cur rent graph format | ||
175 | 005 | ||
176 | 005-025 | ||
177 | RM: 902212 | ||
178 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the CP D Morning Report EM Claims. | ||
179 | 005 | ||
180 | 005-028 | ||
181 | RM: 912164 | ||
182 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the VE Productiv ity Indivi dual Repor t. | ||
183 | 005 | ||
184 | 005-029 | ||
185 | RM: 912167 | ||
186 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the SU Productiv ity Indivi dual Repor t. | ||
187 | 005 | ||
188 | 005-031 | ||
189 | RM: 914733 | ||
190 | As the VE I would li ke to trig ger the ba cking out of the ori ginal char ges for an EDI Corre cted Claim . | ||
191 | 005 | ||
192 | 005-032 | ||
193 | RM: 914735 | ||
194 | As the VE I would li ke to trig ger the ba cking out of the ori ginal char ges for a Manual EDI Corrected Claim. | ||
195 | 005 | ||
196 | 005-033 | ||
197 | RM: 932451 | ||
198 | As the VE I would li ke the sys tem to fro nt end rej ect a subm ission on receipt of a TOB FC 8 when the Original PDI Is Not Valid | ||
199 | 005 | ||
200 | 005-038 | ||
201 | RM: 932472 | ||
202 | As the VE I would li ke the sys tem to kil l the orig inal PDI u pon receip t of a TOB FC 8 when the Origi nal PDI ha s Not Star ted Proces sing | ||
203 | 005 | ||
204 | 005-039 | ||
205 | RM: 937655 | ||
206 | As the VE I would li ke the sys tem to fro nt end rej ect upon R eceipt of submission with a FC 6. | ||
207 | 005 | ||
208 | 005-043 | ||
209 | RM: 937656 | ||
210 | As the VE I want the system to pause the current P DI with a TOB FC 8 w hen All Cl aims / Lin es are Not Complete. | ||
211 | 005 | ||
212 | 005-051 | ||
213 | RM: 937657 | ||
214 | As the VE I want the system to display a n error me ssage when an author ized role attempts t o process an EDI Reo pen claim. | ||
215 | 005 | ||
216 | 005-066 | ||
217 | RM: 937664 | ||
218 | As the R&R VE I want the syste m to verif y all asso ciated cla ims are Co mplete for the Origi nal PDI nu mber enter ed for val idation on the Docum ent ID Scr een when I select to reopen an EDI submi ssion. | ||
219 | 005 | ||
220 | 005-067 | ||
221 | RM: 937665 | ||
222 | As the R&R VE I want the syste m to displ ay an erro r message that reads “Cannot R eOpen PDI” when all associated claims ar e not Comp lete for t he Origina l PDI numb er entered for valid ation on t he Documen t ID Scree n when I s elect to r eopen an E DI submiss ion. | ||
223 | 005 | ||
224 | 005-069 | ||
225 | RM: 937671 | ||
226 | As the R&R VE I want to manual ly input t he Origina l PDI numb er and the Current P DI number on the Doc ument ID s creen (ref er to user story CP& E005-004) when I sel ect to reo pen a manu al EDI sub mission. | ||
227 | 005 | ||
228 | 005-070 | ||
229 | RM: 937672 | ||
230 | As a R&R V E I would like the O riginal PD I and Curr ent PDI fi elds to re vert to Re ad Only on ce the num ber field is populat ed and I a dvance to the next s creen when I select to reopen a manual E DI submiss ion. | ||
231 | 005 | ||
232 | 005-071 | ||
233 | RM: 937673 | ||
234 | As the R&R VE I want the Type of Image t o display as Bill / Invoice (r efer to us er story C PE005-005) when I se lect to re open a man ual EDI su bmission. | ||
235 | 005 | ||
236 | 005-072 | ||
237 | RM: 937674 | ||
238 | As the R&R VE I want to apply the PDI Bu siness Rul e that the entry is 15 digits in total t o manually entered O riginal an d Current PDI number s when I s elect to r eopen a ma nual EDI s ubmission. | ||
239 | 005 | ||
240 | 005-073 | ||
241 | RM: 937675 | ||
242 | As the R&R VE I want to apply the PDI Bu siness Rul e that the first fou r digits r epresents the year, are greate r than or equal to 2 000, and a re not gre ater than the curren t year to manually e ntered Ori ginal and Current PD I numbers when I sel ect to reo pen a manu al EDI sub mission. | ||
243 | 005 | ||
244 | 005-074 | ||
245 | RM: 937676 | ||
246 | As the R&R VE I want to apply the PDI Bu siness Rul e that the 5th, 6th, and 7th d igit repre sents the Julian day and must be 001 thr u 366 to m anually en tered Orig inal and C urrent PDI numbers w hen I sele ct to reop en a manua l EDI subm ission. | ||
247 | 005 | ||
248 | 005-075 | ||
249 | RM: 937677 | ||
250 | As the R&R VE I want to apply the PDI Bu siness Rul e that the 8th and 9 th digit r epresents the PDI Pr ogram Indi cator and must be 90 , 91, 92, or 97 to m anually en tered Orig inal and C urrent PDI numbers w hen I sele ct to reop en a manua l EDI subm ission. | ||
251 | 005 | ||
252 | 005-076 | ||
253 | RM: 937678 | ||
254 | As the R&R VE I want to apply the PDI Bu siness Rul e that the 10th thro ugh 15th d igits are not system validated to manual ly entered Original and Curren t PDI numb ers when I select to reopen a manual EDI submissio n. | ||
255 | 005 | ||
256 | 005-077 | ||
257 | RM: 937679 | ||
258 | As the R&R VE I want to apply the PDI Bu siness Rul e that the Original PDI Number cannot ha ve been pr eviously r eopened t o manually entered O riginal an d Current PDI number s when I s elect to r eopen a ma nual EDI s ubmission. | ||
259 | 005 | ||
260 | 005-079 | ||
261 | RM: 937680 | ||
262 | As the R&R VE I want the syste m to verif y all asso ciated cla ims are Co mplete for the Origi nal PDI nu mber enter ed on the Document I D Screen w hen I sele ct to reop en an EDI submission . | ||
263 | 005 | ||
264 | 005-080 | ||
265 | RM: 937681 | ||
266 | As the R&R VE if I d id not ent er 15 digi ts in tota l in the O riginal or Current P DI field, the system will disp lay "PDI# must be 15 digits" w hen I sele ct to reop en a manua l EDI subm ission. | ||
267 | 005 | ||
268 | 005-081 | ||
269 | RM: 937682 | ||
270 | As the R&R VE if I d id not ent er a Julia n year gre ater than or equal t o 2000, th e system w ill displa y "Julian Year must be year 20 00 or late r" when I select to reopen a m anual EDI submission . | ||
271 | 005 | ||
272 | 005-082 | ||
273 | RM: 937683 | ||
274 | As the R&R VE if I e ntered a J ulian year greater t han the cu rrent year , the syst em will di splay “Jul ian Year c annot be i n the futu re” when I select to reopen a manual EDI submissio n. | ||
275 | 005 | ||
276 | 005-083 | ||
277 | RM: 937684 | ||
278 | As the R&R VE if I d id not ent er a valid Julian da y, the sys tem will d isplay "Ju lian Day m ust be 001 through 3 65" when I select to reopen a manual EDI submissio n. | ||
279 | 005 | ||
280 | 005-084 | ||
281 | RM: 937685 | ||
282 | As the R&R VE if I d id not ent er a valid PDI Progr am Indicat or, the sy stem will display "P DI Program Indicator must be 9 1, 97 (CHA MPVA EDI) or 92, 90 (SB EDI)" when I sel ect to reo pen a manu al EDI sub mission. | ||
283 | 005 | ||
284 | 005-085 | ||
285 | RM: 937686 | ||
286 | As the R&R VE if I e ntered a P DI# that w as previou sly reopen ed the sys tem will d isplay "PD I Number h as already been reop ened" when I select to reopen a manual E DI submiss ion. | ||
287 | 005 | ||
288 | 005-086 | ||
289 | RM: 937687 | ||
290 | As the R& R VE I wan t the syst em to disp lay an err or message that read s “Cannot ReOpen PDI ” when all associate d claims a re not Com plete for the Origin al PDI num ber entere d for vali dation on the Docume nt ID Scre en when I select to reopen a M anual EDI submission . | ||
291 | 005 | ||
292 | 005-087 | ||
293 | RM: 937688 | ||
294 | As the R&R VE I want the EE Bi ll Invoice Screen to not displ ay the Con tinue prom pt when I select to reopen a m anual EDI submission . | ||
295 | 005 | ||
296 | 005-088 | ||
297 | RM: 937689 | ||
298 | As the R&R VE I want the label that read s PDI# to read Curre nt PDI Num ber on the Edit Clai m Data scr een when I select to reopen a manual EDI submissio n so that I can view the Curre nt PDI num ber inform ation. | ||
299 | 005 | ||
300 | 005-095 | ||
301 | RM: 938889 | ||
302 | As the R&R VE I want a new fie ld on the PPR Report to displa y the tota l payment for the Cu rrent PDI number. | ||
303 | CPECC | ||
304 | CPECC4005- 401 | ||
305 | RM: 918057 | ||
306 | As the VA, I need to communica te payment informati on to Fina ncial Mana gement Sys tem (FMS) adjudicati on informa tion regar dless of o utstanding balances so that FM S can prod uce an Exp lanation o f Benefits (EOB). | ||
307 | CPECC | ||
308 | CPECC4005- 402 | ||
309 | RM: 918058 | ||
310 | As the VA, I need to determine if reimbu rsement is due to th e VA by a provider s o that I c an issue a bill of c ollections . | ||
311 | CPECC | ||
312 | CPECC4005- 404 | ||
313 | RM: 920040 | ||
314 | As All Cla ims Proces sing Staff , I need t o Create a payment t o a benefi ciary | ||
315 | CPECC | ||
316 | CPECC4005- 407 | ||
317 | RM: 929961 | ||
318 | If money i s owed fro m the bene , create a bill of c ollections | ||
319 | CPECC | ||
320 | CPECC4005- 408 | ||
321 | RM: 930133 | ||
322 | Create Zer o Balance EOB/Paymen t File | ||
323 | CPECC | ||
324 | CPECC4005- 470 | ||
325 | RM: 942855 | ||
326 | Create Rev ersed/Adju sted 835 S taging Fla t File | ||
327 | User Stori es/Backlog | ||
328 | The Ration al Product backlogs contain al l prioriti zed and ac cepted use r stories. Backlog i tems can b e repriori tized by t he VA at a ny time. T he current backlog i s maintain ed and ava ilable wit hin Ration al. | ||
329 | CP&E Backl og | ||
330 | https:// DNS . URL /ccm/web/p rojects/HA C_CPE%20(C M)#action= com.ibm.te am.apt.vie wPlan&page =com.ibm.t eam.apt.we b.ui.plann edItems&id =_RxBG8Gfa Eee9Yp9RON nEjA&planM ode=com.ib m.team.apt .viewmodes .internal. productBac klog.workB reakdown | ||
331 | Testing Re sponsibili ties | ||
332 | FTC (Devel oper) | ||
333 | Party Resp onsible | ||
334 | Unit/Produ ct/Compone nt Testing | ||
335 | FTC System Quality A ssurance ( SQA) | ||
336 | Build Veri fication T esting | ||
337 | FTC SQA | ||
338 | Functional Testing | ||
339 | FTC SQA | ||
340 | Integratio n/System T esting | ||
341 | FTC SQA | ||
342 | Regression Testing | ||
343 | FTC SQA | ||
344 | Section 50 8 Complian ce Testing | ||
345 | FTC SQA | ||
346 | HAC SQA | ||
347 | Party Resp onsible | ||
348 | Installati on Testing /Build Ver ification | ||
349 | Health Adm inistratio n Center ( HAC) Quali ty Assuran ce (QA) | ||
350 | Security T esting | ||
351 | HAC QA | ||
352 | Performanc e/Load Tes ting | ||
353 | HAC QA | ||
354 | User Accep tance Test ing (UAT) | ||
355 | HAC QA | ||
356 | User Funct ional Test ing (UFT) | ||
357 | VHA CC | ||
358 | Acceptance Criteria | ||
359 | Final Deve lopment Co de Files, Compiled C ode and su pporting d ocumentati on are che cked into the projec t’s Ration al reposit ory | ||
360 | 100% trace ability in Rational | ||
361 | Updated Re quirements Traceabil ity Matrix (RTM) and executed test scrip ts as per plan in Ra tional | ||
362 | 508 Compli ant Checkl ists | ||
363 | Schedule | ||
364 | The Build schedule i s describe d in the s ections be low. Story Points ar e estimate d prior to elaborati on using s tandard Ag ile princi pals and m ay not ref lect actua l hours es timated du ring sprin t planning . | ||
365 | Build 4 Sp rint 1 | ||
366 | CP&E Build 4 | ||
367 | 75 Days | ||
368 | Thu 9/28/17 | ||
369 | Mon 12/19/ 17 | ||
370 | Task Name | ||
371 | Duration | ||
372 | Start | ||
373 | Finish | ||
374 | Build 4 Sp rint 1 | ||
375 | 12 Days | ||
376 | Thu 9/28/17 | ||
377 | Tue 10/10 /17 | ||
378 | Team | ||
379 | Descriptio n | ||
380 | Epic | ||
381 | Sub Epic | ||
382 | User Story | ||
383 | Story Poin ts | ||
384 | Hours | ||
385 | Team 1 | ||
386 | As the VE I want the system to display a n error me ssage when an author ized role attempts t o process an EDI Reo pen claim | ||
387 | 005 | ||
388 | N/A | ||
389 | 005-051 | ||
390 | 5 | ||
391 | 40 | ||
392 | |||
393 | As the R&R VE I want to manual ly input t he Origina l PDI numb er and the Current P DI number on the Doc ument ID s creen (ref er to user story CP& E005-004) when I sel ect to reo pen a manu al EDI sub mission. | ||
394 | 005 | ||
395 | N/A | ||
396 | 005-069 | ||
397 | 8 | ||
398 | 50 | ||
399 | |||
400 | As a R&R V E I would like the O riginal PD I and Curr ent PDI fi elds to re vert to Re ad Only on ce the num ber field is populat ed and I a dvance to the next s creen when I select to reopen a manual E DI submiss ion | ||
401 | 005 | ||
402 | N/A | ||
403 | 005-070 | ||
404 | 8 | ||
405 | 50 | ||
406 | |||
407 | As the R&R VE I want the Type of Image t o display as Bill / Invoice (r efer to us er story C PE005-005) when I se lect to re open a man ual EDI su bmission. | ||
408 | 005 | ||
409 | N/A | ||
410 | 005-071 | ||
411 | 5 | ||
412 | 42 | ||
413 | |||
414 | As the VE I would li ke the sys tem to fro nt end rej ect a subm ission on receipt of a TOB FC 8 when the Original PDI Is Not Valid | ||
415 | 005 | ||
416 | N/A | ||
417 | 005-033 | ||
418 | 5 | ||
419 | 42 | ||
420 | |||
421 | As the VE I would li ke the sys tem to kil l the orig inal PDI u pon receip t of a TOB FC 8 when the Origi nal PDI ha s Not Star ted Proces sing | ||
422 | 005 | ||
423 | N/A | ||
424 | 005-038 | ||
425 | 5 | ||
426 | 42 | ||
427 | Team 2 | ||
428 | As the R&R VE if I d id not ent er 15 digi ts in tota l in the O riginal or Current P DI field, the system will disp lay "PDI# must be 15 digits" w hen I sele ct to reop en a manua l EDI subm ission. | ||
429 | 005 | ||
430 | N/A | ||
431 | 005-080 | ||
432 | 8 | ||
433 | 50 | ||
434 | |||
435 | As the R&R VE I want to apply the PDI Bu siness Rul e that the first fou r digits r epresents the year, are greate r than or equal to 2 000, and a re not gre ater than the curren t year to manually e ntered Ori ginal and Current PD I numbers when I sel ect to reo pen a manu al EDI sub mission. | ||
436 | 005 | ||
437 | N/A | ||
438 | 005-073 | ||
439 | 8 | ||
440 | 50 | ||
441 | |||
442 | As the R&R VE I want to apply the PDI Bu siness Rul e that the 5th, 6th, and 7th d igit repre sents the Julian day and must be 001 thr u 366 to m anually en tered Orig inal and C urrent PDI numbers w hen I sele ct to reop en a manua l EDI subm ission. | ||
443 | 005 | ||
444 | N/A | ||
445 | 005-074 | ||
446 | 8 | ||
447 | 50 | ||
448 | |||
449 | As the R&R VE I want to apply the PDI Bu siness Rul e that the 8th and 9 th digit r epresents the PDI Pr ogram Indi cator and must be 90 , 91, 92, or 97 to m anually en tered Orig inal and C urrent PDI numbers w hen I sele ct to reop en a manua l EDI subm ission. | ||
450 | 005 | ||
451 | N/A | ||
452 | 005-075 | ||
453 | 8 | ||
454 | |||
455 | |||
456 | As the VE I would li ke to trig ger the ba cking out of the ori ginal char ges for an EDI Corre cted Claim . | ||
457 | 005 | ||
458 | N/A | ||
459 | 005-031 | ||
460 | 5 | ||
461 | 35 | ||
462 | |||
463 | As the VE I would li ke to trig ger the ba cking out of the ori ginal char ges for a Manual EDI Corrected Claim | ||
464 | 005 | ||
465 | N/A | ||
466 | 005-032 | ||
467 | 5 | ||
468 | 38 | ||
469 | Team 3 | ||
470 | As the VE I would li ke the sys tem to fro nt end rej ect upon R eceipt of submission with a FC 6 | ||
471 | 005 | ||
472 | N/A | ||
473 | 005-039 | ||
474 | 8 | ||
475 | 58 | ||
476 | |||
477 | As the VE I want the system to pause the current P DI with a TOB FC 8 w hen All Cl aims / Lin es are Not Complete | ||
478 | 005 | ||
479 | N/A | ||
480 | 005-043 | ||
481 | 5 | ||
482 | 42 | ||
483 | |||
484 | As the R&R VE I want to apply the PDI Bu siness Rul e that the 10th thro ugh 15th d igits are not system validated to manual ly entered Original and Curren t PDI numb ers when I select to reopen a manual EDI submissio n. | ||
485 | 005 | ||
486 | N/A | ||
487 | 005-076 | ||
488 | 8 | ||
489 | 50 | ||
490 | |||
491 | As the R&R VE I want to apply the PDI Bu siness Rul e that the Original PDI Number cannot ha ve been pr eviously r eopened t o manually entered O riginal an d Current PDI number s when I s elect to r eopen a ma nual EDI s ubmission. | ||
492 | 005 | ||
493 | N/A | ||
494 | 005-077 | ||
495 | 8 | ||
496 | 50 | ||
497 | |||
498 | As the R&R VE I want the syste m to verif y all asso ciated cla ims are Co mplete for the Origi nal PDI nu mber enter ed on the Document I D Screen w hen I sele ct to reop en an EDI submission . | ||
499 | 005 | ||
500 | N/A | ||
501 | 005-079 | ||
502 | 5 | ||
503 | 40 | ||
504 | D: Sprint Plan | ||
505 | Fri 9/22/1 7 | ||
506 | Sprint Kic koff/Plann ing (All T eams) | ||
507 | 4-6 Hrs | ||
508 | |||
509 | Thu 9/28/1 7 | ||
510 | Sprint 1 B acklog Gro oming (All Teams) | ||
511 | 1 Hr | ||
512 | |||
513 | Thu 9/21/1 7 | ||
514 | Sprint 1 S print Revi ew (All Te ams) | ||
515 | 1 Hr | ||
516 | |||
517 | Thu 9/21/1 7 | ||
518 | |||
519 | |||
520 | |||
521 | Build 4 Sp rint 2 | ||
522 | Build 4 Sp rint 2 | ||
523 | 13 Days | ||
524 | Wed 10/11/ 17 | ||
525 | Tue 10/ 24/17 | ||
526 | Team | ||
527 | Descriptio n | ||
528 | Epic | ||
529 | Sub Epic | ||
530 | User Story | ||
531 | Story Poin ts | ||
532 | Hours | ||
533 | Team 1 | ||
534 | As the Hea lth Claims Reimburse ment Group I would l ike to add a Program Indicator to the PD I to tell the system to ReOpen EDI. | ||
535 | 005 | ||
536 | N/A | ||
537 | 005-001 | ||
538 | 13 | ||
539 | 60 | ||
540 | |||
541 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the VE Productiv ity Indivi dual Repor t. | ||
542 | 005 | ||
543 | N/A | ||
544 | 005-028 | ||
545 | 8 | ||
546 | 48 | ||
547 | |||
548 | As the R&R VE I want to apply the PDI Bu siness Rul e that the entry is 15 digits in total t o manually entered O riginal an d Current PDI number s when I s elect to r eopen a ma nual EDI s ubmission. | ||
549 | 005 | ||
550 | N/A | ||
551 | 005-072 | ||
552 | 5 | ||
553 | 42 | ||
554 | |||
555 | As the R&R VE I want a new fie ld on the PPR Report to displa y the tota l payment for the Cu rrent PDI number. | ||
556 | 005 | ||
557 | N/A | ||
558 | 005-095 | ||
559 | 8 | ||
560 | 50 | ||
561 | Team 2 | ||
562 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the VE Productiv ity Summar y Report. | ||
563 | 005 | ||
564 | N/A | ||
565 | 005-022 | ||
566 | 5 | ||
567 | 42 | ||
568 | |||
569 | As the R&R VE I want the syste m to verif y all asso ciated cla ims are Co mplete for the Origi nal PDI nu mber enter ed for val idation on the Docum ent ID Scr een when I select to reopen an EDI submi ssion. | ||
570 | 005 | ||
571 | N/A | ||
572 | 005-066 | ||
573 | 8 | ||
574 | 50 | ||
575 | |||
576 | As the R&R VE I want the syste m to displ ay an erro r message that reads “Cannot R eOpen PDI” when all associated claims ar e not Comp lete for t he Origina l PDI numb er entered for valid ation on t he Documen t ID Scree n when I s elect to r eopen an E DI submiss ion. | ||
577 | 005 | ||
578 | N/A | ||
579 | 005-067 | ||
580 | 8 | ||
581 | 50 | ||
582 | Team 3 | ||
583 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the Da ily Hourly Processin g Report. | ||
584 | 005 | ||
585 | N/A | ||
586 | 005-023 | ||
587 | 8 | ||
588 | 55 | ||
589 | |||
590 | As the Hea lth Claims Reimburse ment Group I would l ike a new menu optio n on the D aily Hourl y Processi ng Report to display EDI RO in formation in the cur rent graph format | ||
591 | 005 | ||
592 | N/A | ||
593 | 005-023a | ||
594 | 5 | ||
595 | 42 | ||
596 | |||
597 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the CP D Morning Report EM Claims. | ||
598 | 005 | ||
599 | N/A | ||
600 | 005-025 | ||
601 | 5 | ||
602 | 42 | ||
603 | |||
604 | As the Hea lth Claims Reimburse ment Group I would l ike EDI Re Open data to display on the VE Productiv ity Indivi dual Repor t | ||
605 | 005 | ||
606 | N/A | ||
607 | 005-029 | ||
608 | 5 | ||
609 | 42 | ||
610 | D: Sprint Plan | ||
611 | Fri 9/22/1 7 | ||
612 | Sprint Kic koff/Plann ing (All T eams) | ||
613 | 4-6 Hrs | ||
614 | |||
615 | Wed 10/11/ 17 | ||
616 | Sprint 2 B acklog Gro oming (All Teams) | ||
617 | 1 Hr | ||
618 | |||
619 | Thu 9/21/1 7 | ||
620 | Sprint 2 S print Revi ew (All Te ams) | ||
621 | 1 Hr | ||
622 | |||
623 | Thu 9/21/1 7 | ||
624 | Build 4 Sp rint 3 | ||
625 | CP&E Build 4 | ||
626 | 75 Days | ||
627 | Thu 9/28/17 | ||
628 | Mon 12/19/ 17 | ||
629 | Task Name | ||
630 | Duration | ||
631 | Start | ||
632 | Finish | ||
633 | Build 4 Sp rint 3 | ||
634 | 14 Days | ||
635 | Wed 10/25/17 | ||
636 | Tue 11/07 /17 | ||
637 | Team | ||
638 | Descriptio n | ||
639 | Epic | ||
640 | Sub Epic | ||
641 | User Story | ||
642 | Story Poin ts | ||
643 | Hours | ||
644 | Team 1 | ||
645 | As the R&R VE if I d id not ent er a Julia n year gre ater than or equal t o 2000, th e system w ill displa y "Julian Year must be year 20 00 or late r" when I select to reopen a m anual EDI submission . | ||
646 | 005 | ||
647 | N/A | ||
648 | 005-081 | ||
649 | 5 | ||
650 | 40 | ||
651 | |||
652 | As the R&R VE if I e ntered a J ulian year greater t han the cu rrent year , the syst em will di splay “Jul ian Year c annot be i n the futu re” when I select to reopen a manual EDI submissio n. | ||
653 | 005 | ||
654 | N/A | ||
655 | 005-082 | ||
656 | 8 | ||
657 | 50 | ||
658 | |||
659 | As the VA, I need to communica te payment informati on to Fina ncial Mana gement Sys tem (FMS) adjudicati on informa tion regar dless of o utstanding balances so that FM S can prod uce an Exp lanation o f Benefits (EOB). | ||
660 | CPECC | ||
661 | N/A | ||
662 | CPECC4005- 401 | ||
663 | 8 | ||
664 | 50 | ||
665 | |||
666 | As the VA, I need to determine if reimbu rsement is due to th e VA by a provider s o that I c an issue a bill of c ollections . | ||
667 | CPECC | ||
668 | N/A | ||
669 | CPECC4005- 402 | ||
670 | 5 | ||
671 | 40 | ||
672 | |||
673 | As All Cla ims Proces sing Staff , I need t o Create a payment t o a benefi ciary | ||
674 | CPECC | ||
675 | N/A | ||
676 | CPECC4005- 404 | ||
677 | 5 | ||
678 | 40 | ||
679 | |||
680 | If money i s owed fro m the bene , create a bill of c ollections | ||
681 | CPECC | ||
682 | N/A | ||
683 | CPECC4005- 407 | ||
684 | 5 | ||
685 | 40 | ||
686 | Team 2 | ||
687 | As the R&R VE if I e ntered a P DI# that w as previou sly reopen ed the sys tem will d isplay "PD I Number h as already been reop ened" when I select to reopen a manual E DI submiss ion. | ||
688 | 005 | ||
689 | N/A | ||
690 | 005-085 | ||
691 | 5 | ||
692 | 42 | ||
693 | |||
694 | As the R&R VE I want the syste m to displ ay an erro r message that reads “Cannot R eOpen PDI” when all associated claims ar e not Comp lete for t he Origina l PDI numb er entered for valid ation on t he Documen t ID Scree n when I s elect to r eopen a Ma nual EDI s ubmission. | ||
695 | 005 | ||
696 | N/A | ||
697 | 005-086 | ||
698 | 5 | ||
699 | 42 | ||
700 | |||
701 | As the R&R VE I want the EE Bi ll Invoice Screen to not displ ay the Con tinue prom pt when I select to reopen a m anual EDI submission . | ||
702 | 005 | ||
703 | N/A | ||
704 | 005-087 | ||
705 | 5 | ||
706 | 42 | ||
707 | |||
708 | As the R&R VE if I d id not ent er a valid Julian da y, the sys tem will d isplay "Ju lian Day m ust be 001 through 3 65" when I select to reopen a manual EDI submissio n. | ||
709 | 005 | ||
710 | N/A | ||
711 | 005-083 | ||
712 | 8 | ||
713 | 50 | ||
714 | Team 3 | ||
715 | As the R&R VE if I d id not ent er a valid PDI Progr am Indicat or, the sy stem will display "P DI Program Indicator must be 9 1, 97 (CHA MPVA EDI) or 92, 90 (SB EDI)" when I sel ect to reo pen a manu al EDI sub mission. | ||
716 | 005 | ||
717 | N/A | ||
718 | 005-084 | ||
719 | 8 | ||
720 | 58 | ||
721 | |||
722 | As the R&R VE I want the label that read s PDI# to read Curre nt PDI Num ber on the Edit Clai m Data scr een when I select to reopen a manual EDI submissio n so that I can view the Curre nt PDI num ber inform ation. | ||
723 | 005 | ||
724 | N/A | ||
725 | 005-088 | ||
726 | 5 | ||
727 | 40 | ||
728 | |||
729 | Create Zer o Balance EOB/Paymen t File | ||
730 | CPECC | ||
731 | N/A | ||
732 | CPECC4005- 408 | ||
733 | 5 | ||
734 | 40 | ||
735 | |||
736 | Create Rev ersed / Ad justed 835 Staging F lat File | ||
737 | CPECC | ||
738 | N/A | ||
739 | CPECC4005- 470 | ||
740 | 5 | ||
741 | 40 | ||
742 | D: Sprint Plan | ||
743 | Thu 10/06/ 17 | ||
744 | Sprint Kic koff/Plann ing (All T eams) | ||
745 | 4-6 Hrs | ||
746 | |||
747 | Wed 10/25/ 17 | ||
748 | Sprint 3 B acklog Gro oming (All Teams) | ||
749 | 1 Hr | ||
750 | |||
751 | Thu 10/05/ 17 | ||
752 | Sprint 3 S print Revi ew (All Te ams) | ||
753 | 1 Hr | ||
754 | |||
755 | Thu 10/06/ 17 | ||
756 | |||
757 | Sprint Cer emonies | ||
758 | Meeting Na me | ||
759 | Date | ||
760 | Time | ||
761 | Duration | ||
762 | Attendees | ||
763 | Standing S print Cere monies/Mee tings | ||
764 | Sprint Kic koffVetera n-focused Integratio n Process (VIP) Spri nt Plannin g | ||
765 | First Day of Sprint | ||
766 | Various(We d) | ||
767 | 1 Hr per T eam | ||
768 | FTC Team R epsVA PMVA PO | ||
769 | Daily Scru m | ||
770 | Daily | ||
771 | Mornings | ||
772 | 10 Mins | ||
773 | FTC Team M embersVA R epresentat ives Welco me | ||
774 | Scrum of S crums | ||
775 | Daily | ||
776 | 11:30 | ||
777 | 30 Mins | ||
778 | FTC Team R epsVA PMVA PO | ||
779 | Sprint Bac klog Groom ing/Planni ng | ||
780 | Bi-Weekly | ||
781 | 3:00Thu | ||
782 | 1 Hr | ||
783 | FTC Team R epsVA PMVA POVA BA | ||
784 | Sprint Rev iew | ||
785 | At Sprint End | ||
786 | 2:00Tue | ||
787 | 1 Hr | ||
788 | FTC Team R epsVA PMVA PO | ||
789 | |||
790 | |||
791 | |||
792 | Build 4 Pl anning | ||
793 | Standing B uild Plann ing Sessio ns/Meeting s/Delivera bles | ||
794 | Build 4 Pl anning | ||
795 | Timeframe | ||
796 | Date | ||
797 | Duration | ||
798 | Attendees | ||
799 | Build Plan 4 Backlog Review | ||
800 | Within 3 W eeks Prior to Build Start | ||
801 | 9/07/17 | ||
802 | 1 Hr | ||
803 | FTC Team R epsVA PMVA POVA BA | ||
804 | Build Plan 4 Plannin g Session | ||
805 | Within 3 W eeks Prior to Build Start | ||
806 | 9/12/17 | ||
807 | 1 Hr | ||
808 | FTC Team R epsVA PMVA POVA BA | ||
809 | Build Plan 4 Review | ||
810 | Within 2 W eeks Prior to Build Start | ||
811 | 9/14/17 | ||
812 | 1 Hr | ||
813 | FTC Team R epsVA PMVA POVA BA | ||
814 | |||
815 | Dependenci es | ||
816 | HAC Full T ime Employ ee (FTE) r esources w ill be req uired to a nswer spec ific techn ical quest ions regar ding HAC i diosyncras ies and sp ecific imp lementatio n issues. | ||
817 | QA and UAT testing i s dependen t upon HAC QA resour ce and Sub ject Matte r Expert ( SME) avail ability. | ||
818 | Risks & Is sues | ||
819 | Identified Risks | ||
820 | IF: the re fresh of t he HAC env ironments are not co nsidered i n the sche dule, THEN : there wi ll be a de lay in the completio n of devel opment by the contra cted date. | ||
821 | IF: multip le develop ers work o n the same code modu le and pus h their ch anges into productio n, THEN: t he last de veloper to push a ch ange into production will over write the work of th e other de velopers. | ||
822 | Identified Issues | ||
823 | None | ||
824 | Constraint s | ||
825 | Developmen t timefram e will dep end on HAC QA and UA T testing schedule. | ||
826 | Definition of Done | ||
827 | Sprint wor k product deliverabl es are lis ted above. | ||
828 | Final Deve lopment Co de Files, Compiled C ode and su pporting d ocumentati on are che cked into the projec t’s Ration al reposit ory (0008A M). | ||
829 | 100% trace ability in Rational | ||
830 | Creation o f all the iterative Release Pa ckage (008 AP) docume ntation as sociated w ith Build 4 required for a fut ure releas e to produ ction (e.g . Installa tion Guide and User Manual) | ||
831 | Updated RT M and exec uted test scripts as per plan in Rationa l | ||
832 | Defects, f unctionali ty, and us er satisfa ction norm ally ident ified and resolved d uring a sp rint or re solved in the follow ing sprint will accu mulate thr oughout th e build if VA is una ble to acc omplish sp rint by sp rint SQA/U AT testing . | ||
833 | Defects fo und during SQA and U AT will im pact the v olume of w ork to be accomplish ed during Build 4 or when the VA is able to perfor m SQA/UAT testing. T his dynami c must be anticipate d and plan ned. | ||
834 | In followi ng the Agi le process defects f ound durin g a sprint that cann ot be reso lved withi n the spri nt are pla ced in the build bac klog and w ill be wor ked in the next spri nt and the technical reasons w hy the Use r Story wi th defects could not be finish ed within the sprint will be e xplained d uring the sprint ret rospective . | ||
835 | Build 4 De liverables | ||
836 | All comple ted Sprint work prod uct delive rables are checked i nto the pr oject’s Ra tional rep ository to be update d and main tained as project mo ves forwar d. | ||
837 | Build 4 Re lease Plan ning Packa ge (0008AF ) | ||
838 | Build 4 Sp rint Plans (0008AG) | ||
839 | Build 4 Sp rint Burn down and V elocity ch arts (0008 AH) | ||
840 | Build 4 50 8 Certific ation (000 8AK) | ||
841 | Build 4 Ac ceptance F orm (0008A N) | ||
842 | Build 4 Re lease Pack age (0008A P) |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.