Produced by Araxis Merge on 9/25/2018 2:34:38 PM Eastern Daylight 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 | MHLTH_CLOZ_MOD _SRC.zip\MHLTH_CLOZ_MOD _SRC | Cloz Mod - Configuration Management Plan.docx | Tue Aug 14 18:03:08 2018 UTC |
2 | MHLTH_CLOZ_MOD _SRC.zip\MHLTH_CLOZ_MOD _SRC | Cloz Mod - Configuration Management Plan.docx | Tue Sep 25 15:48:16 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 5 | 1320 |
Changed | 4 | 10 |
Inserted | 0 | 0 |
Removed | 0 | 0 |
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 | Department of Vetera ns Affairs | |
2 | Mental Hea lth (MHLTH ) | |
3 | Clozapine Modernizat ion | |
4 | Product (S ystem) Con figuration Managemen t Plan | |
5 | ||
6 | ||
7 | ||
8 | ||
9 | Department of Vetera ns Affairs | |
10 | Office of Informatio n and Tech nology (OI T) | |
11 | EPMO Confi guration M anagement Team | |
12 | ||
13 | August 201 8 | |
14 | ||
15 | Version 1. 12 | |
16 | Revision H istory | |
17 | ||
18 | Date | |
19 | Revision | |
20 | Descriptio n | |
21 | Author | |
22 | 08/8/2018 | |
23 | 1.12 | |
24 | Updated da tes; added documents locations ; updated baselines details | |
25 | Terrance H ardison | |
26 | 07/25/2018 | |
27 | 1.11 | |
28 | Updated da tes; added Builds 5 & 6 (optio nal tasks builds) an d associat ed sprints | |
29 | Terrance H ardison | |
30 | 07/13/2018 | |
31 | 1.10 | |
32 | Updated da tes | |
33 | Mike Stall ings | |
34 | 06/13/2018 | |
35 | 1.9 | |
36 | Update dat es | |
37 | Mike Stall ings | |
38 | 05/14/2018 | |
39 | 1.8 | |
40 | Update dat es | |
41 | Mike Stall ings | |
42 | 04/15/2018 | |
43 | 1.7 | |
44 | Update dat es | |
45 | Mike Stall ings | |
46 | 03/26/2018 | |
47 | 1.6 | |
48 | Transfer i nformation to the ne w CMP temp late; upda te to name space name | |
49 | Ursula Wil son, EPMO CM | |
50 | 03/15/2018 | |
51 | 1.5 | |
52 | Updated da tes | |
53 | Mike Stall ings | |
54 | 02/15/2018 | |
55 | 1.4 | |
56 | Updated da tes | |
57 | Mike Stall ings | |
58 | 01/15/2018 | |
59 | 1.3 | |
60 | Updated da tes | |
61 | Mike Stall ings | |
62 | 12/15/2017 | |
63 | 1.2 | |
64 | Updated da tes | |
65 | Mike Stall ings | |
66 | 11/15/2017 | |
67 | 1.1 | |
68 | November 2 017 | |
69 | B3 Group, Inc. | |
70 | 10/20/2017 | |
71 | 1.0 | |
72 | Initial ve rsion | |
73 | B3 Group, Inc. | |
74 | ||
75 | ||
76 | ||
77 | ||
78 | ||
79 | ||
80 | ||
81 | ||
82 | ||
83 | ||
84 | ||
85 | ||
86 | ||
87 | ||
88 | ||
89 | ||
90 | ||
91 | Table of C ontents | |
92 | Mental Hea lth (MHLTH )ii | |
93 | Clozapine Modernizat ionii | |
94 | 1.Overview 3 | |
95 | 1.1.Scope3 | |
96 | 1.2.Refere nces4 | |
97 | 1.3.Acrony ms5 | |
98 | 1.4.Glossa ry5 | |
99 | 2.Configur ation Mana gement6 | |
100 | 2.1.Respon sibilities 6 | |
101 | 2.2.Tools Identifica tion and L ocation8 | |
102 | 2.3.Interf ace/Depend ency Manag ement10 | |
103 | 2.4.CCM Im plementati on10 | |
104 | 2.4.1CCM E nvironment Planning and Setup1 0 | |
105 | 2.4.2Devel opment Sup port11 | |
106 | 2.4.3Relea se Prepara tion11 | |
107 | 2.4.4Proje ct Closeou t12 | |
108 | 3.Configur ation Iden tification 12 | |
109 | 3.1.Naming Conventio ns12 | |
110 | 3.2.Config uration Co ntrol (Ver sion and B aseline Ma nagement)1 4 | |
111 | 3.2.1Sourc e Code – N /A for Inf rastructur e14 | |
112 | 3.2.2Docum entation14 | |
113 | 3.2.3Envir onment – N /A for Inf rastructur e14 | |
114 | 3.3.Change Managemen t15 | |
115 | 3.3.1Story and Task Management 15 | |
116 | 3.3.2Defec t Manageme nt15 | |
117 | 3.3.3Risk/ Issue Mana gement16 | |
118 | 3.4.Status Accountin g16 | |
119 | 3.4.1Dashb oards16 | |
120 | 3.4.2Queri es16 | |
121 | 3.4.3Gener al Status Reports16 | |
122 | 3.5.Config uration Au dits and R eviews17 | |
123 | 3.6.Releas e Manageme nt17 | |
124 | 3.6.1Elect ronic Rele ase Packag e – N/A fo r Infrastr ucture18 | |
125 | 3.6.2Versi on Descrip tion Docum ent18 | |
126 | 3.7.Traini ng18 | |
127 | 3.8.CCM Ba ckup and D isaster Re covery Pla ns18 | |
128 | ||
129 | Overview | |
130 | Product be ing modifi ed: | |
131 | Mental Hea lth (MHLTH ) | |
132 | Project Na me: | |
133 | Clozapine Modernizat ion | |
134 | Technologi es to be u sed: | |
135 | Eclipse | |
136 | Visual Stu dio 2017 | |
137 | ||
138 | Scope | |
139 | Configurat ion Items (CIs): | |
140 | Documentat ion / Sour ce Code | |
141 | Builds/Rel eases | |
142 | Other | |
143 | Documentat ion | |
144 | Product Ba selines | |
145 | Folder set up | |
146 | Baseline | |
147 | Release Pa ckages | |
148 | Timeline s etup | |
149 | Software ( SW) | |
150 | ||
151 | Release Pl an setup | |
152 | ||
153 | ||
154 | ||
155 | Required C onfigurati on Managem ent Activi ties: | |
156 | Documentat ion / Sour ce Code | |
157 | Change Man agement | |
158 | Builds/Rel eases | |
159 | Other | |
160 | Create/Mai ntain CCM Repository | |
161 | Create/Mai ntain CCM Documentat ion | |
162 | Audit Proj ect Docume ntation fo r Naming S tandards | |
163 | Identify/D ocument Co nfiguratio n Items | |
164 | Version/Ba seline Man agement | |
165 | Periodical ly review repositori es for fil es that ha ve been ch ecked out for an ext ended peri od of time | |
166 | Perform Ch ange Manag ement | |
167 | Audit Chan ge Request s for Accu racy and C ompletenes s | |
168 | Create Que ries, Repo rts and Me trics from CCM Tool, as needed | |
169 | Create/Mai ntain Stre ams and Ba selines | |
170 | Package an d Release Documentat ion | |
171 | ||
172 | Develop/Ma intain CCM Dashboard s | |
173 | Train/Advi se Team Me mbers on C CM Process es and Pro cedures | |
174 | Provide Fi rst Line C CM Tools S upport | |
175 | Perform CC M Tool Acc ess Manage ment | |
176 | Perform Au dits | |
177 | References | |
178 | The follow ing docume nts provid e referenc e material for backg round info rmation on ly. In cas e of confl ict, the O ffice of I nformation and Techn ology docu ments is t he guidanc e document otherwise ; this Con figuration Managemen t Plan wil l take pre cedence. C ontact the CCM team for instru ctions on how to obt ain copies of the re leased ver sion(s) of these doc uments. | |
179 | Office of Informatio n and Tech nology VA Directive 6004 - Con figuration , Change, and Releas e Manageme nt Program s | |
180 | Office of Informatio n and Tech nology Con figuration Managemen t Process, Change Ma nagement P rocess and Release M anagement Process. Process As set Librar y (PAL) (h ttp:// DNS . URL /process/h ome.aspx) | |
181 | Technical Reference Models (ht tp:// DNS . URL/vdl/ap pl i ca t ion .
|
|
182 | Office of Informatio n and Tech nology (OI T) End-Use r Document ation Stan dards | |
183 | 192-039 In terface Co ntrol Regi stration a nd Approva l Document | |
184 | Displaying Sensitive Data Guid e | |
185 | CM_Doc_Map | |
186 | VA Rationa l Tools Te am Instruc tional Doc umentation (http:// DNS . URL /communiti es/OSCTM/t oolsmgmt/R ational%20 Tools/Docu ments/Form s/AllItems .aspx) | |
187 | ||
188 | Acronyms | |
189 | VA acronym list: https:// DNS . URL /acronyms/ index.cfm | |
190 | CCM relate d acronyms : CCM Acro nym Table | |
191 | ||
192 | Glossary | |
193 | VistA Infr astructure glossary: http:// DNS . URL /iss/gloss ary.asp | |
194 | ||
195 | ||
196 | ||
197 | ||
198 | Configurat ion Manage ment | |
199 | ||
200 | Responsibi lities | |
201 | Anyone dev eloping or maintaini ng artifac ts for thi s project is require d to follo w proper v ersion con trol and c hange mana gement pro cedures de fined in t he CCM Pla n and work instructi ons. | |
202 | Role | |
203 | Name | |
204 | CfM Respon sibility | |
205 | Product Ow ner | |
206 | Dr. Kathle en M. Lyse ll | |
207 | Supports c hange mana gement by defining a nd approvi ng the con tent of th e Product Backlog | |
208 | Establishe s the prio rity of wo rk items | |
209 | Scrum Mast er | |
210 | Jennifer G ulick | |
211 | Defines th e Timeline s, Iterati ons and Pl ans for th e project | |
212 | Supports c hange mana gement thr ough Backl og Groomin g | |
213 | Manages pr oject scop e by facil itating Sp rint Plann ing | |
214 | Program Ma nager (Pgm Mgr)/ | |
215 | Project Ma nagement ( PM) | |
216 | VA PgmMgr: | |
217 | Kristen T emplet | |
218 | ||
219 | VA PM: | |
220 | Kristen Te mplet | |
221 | ||
222 | Vendor Pgm Mgr: | |
223 | Chad Hensl ey | |
224 | ||
225 | Vendor PM: | |
226 | Pam Price | |
227 | Ensures pr oper execu tion of th e CCM Plan | |
228 | Oversees t he CCM pro cess | |
229 | Ensures te am members have comp leted the training f or the Rat ional Tool s | |
230 | Supports c hange mana gement pro tocol defi ned by CCM | |
231 | Works with Product O wner on Pr oduct Back log | |
232 | Identifies dependent projects | |
233 | Establishe s/revises list of re quired art ifacts | |
234 | Configurat ion Manage r | |
235 | ||
236 | Terrance H ardison | |
237 | Matthew Hu mphreys (C fM Support ) | |
238 | Educates p roject tea m members in CCM “be st practic es” | |
239 | Establishe s, promote s, and rel eases base lines | |
240 | Works with the Enter prise Tool s Team to create and administe r the CCM tool envir onment | |
241 | Performs o r validate s interim and final builds | |
242 | Assist in preparing release pa ckage, rel ease archi ves and Ve rsion Desc ription Do cuments (V DD) | |
243 | Accountabl e for inst ituting th e establis hed proces ses and re porting pr ogress sta tistics ba sed on cha nge reques ts | |
244 | Conducts C CM audits and necess ary status accountin g related to the pro duct at sc heduled mi lestones | |
245 | Requests J azz access removal o r role cha nges for a ny team me mbers who are incomi ng or remo ved from t he project | |
246 | Developmen t Manager/ Leads | |
247 | ||
248 | Randy Poyn ter/ Mike Henderson | |
249 | Submits bu ild/releas e requests | |
250 | Coordinate s developm ent activi ties and a ssigns tas ks | |
251 | Ensures CC M Plan and work inst ructions a re impleme nted and f ollowed fo r all soft ware, docu mentation, and/or an y other co mponents f or which t hey are re sponsible | |
252 | Ensures al l develope rs work wi thin the s pecified C CM process and relat ed guideli nes as spe cified in the CCM Pl an and wor k instruct ions | |
253 | Developers /System Ad ministrati on/Functio nal/ Techn ical Analy sts/DBAs/S ystem Admi nistration | |
254 | ||
255 | Kathey Eng lish (DBA) | |
256 | Updates al l assigned work item s with acc urate, det ailed info rmation | |
257 | Maintains source cod e and docu mentation within the VA enterp rise CCM t ool | |
258 | Apply link s between artifacts as appropr iate | |
259 | Technical Writer | |
260 | ||
261 | Jennifer G ulick | |
262 | Develops a nd maintai ns technic al deliver able docum entation w ithin the VA enterpr ise CCM to ol | |
263 | Updates al l assigned work item s with acc urate, det ailed info rmation | |
264 | Software Q uality Ass urance Man ager | |
265 | ||
266 | Susan Taji li | |
267 | Ensures al l SQA Anal ysts work within the CCM Plan and work i nstruction s | |
268 | Verifies t hat only C CM-approve d delivera bles are i nstalled i nto the te st environ ment(s) | |
269 | Ensures th at SQA Ana lysts are always tes ting from official C CM deliver ables | |
270 | Reviews st atus accou nting rela ted to the project | |
271 | Reviews de liverable artifacts | |
272 | Software Q uality Ass urance Ana lysts/Test ing Analys t/Testing Service An alyst | |
273 | ||
274 | Paul Crows on/ Erika Sarber | |
275 | Tests inst alled rele ases, as C CM provide s releases from deve lopment | |
276 | Updates wo rk items a ssigned to them acco rding to t est activi ty results | |
277 | Determines Pass/Fail for each work item scheduled for a rele ase | |
278 | Opens defe ct work it ems for an y newly di scovered p roblems du ring testi ng | |
279 | Apply link s between artifacts as appropr iate | |
280 | Release Ma nager/Impl ementation Team/EVS/ Operations Team/Depl oyment Tea m-Enterpri se Product Support ( EPS) | |
281 | ||
282 | TBD | |
283 | Coordinate s the rele ase and de ployment o f software to the ex isting sit es and the newly act ivated sit es followi ng CCM Pla n and work instructi ons | |
284 | ||
285 | Tools Iden tification and Locat ion | |
286 | Tools / Ve rsion | |
287 | If VA Ente rprise: | |
288 | If NOT VA Enterprise : | |
289 | Waiver? | |
290 | Change Man agement | |
291 | Jazz Proje ct(s): | |
292 | MHLTH (CM) | |
293 | ||
294 | Team Area( s): | |
295 | Clozapine | |
296 | MOD | |
297 | Is it insi de VA fire wall? | |
298 | Physical s erver loca tion: | |
299 | Company/ Bldg/City/ State | |
300 | Server nam e: | |
301 | Contact pe rson for a ccess: | |
302 | Name/Ph one/email | |
303 | Are there plans to m igrate dat a to VA En terprise T ool? | |
304 | If yes, wh en? | |
305 | ||
306 | Source | |
307 | Management | |
308 | Jazz Proje ct(s): | |
309 | MHLTH (CM) | |
310 | ||
311 | Team Area( s): | |
312 | Clozapine | |
313 | MOD | |
314 | Is it insi de VA fire wall? | |
315 | Physical s erver loca tion: | |
316 | Company/ Bldg/City/ State | |
317 | Server nam e: | |
318 | Contact pe rson for a ccess: | |
319 | Name/Ph one/email | |
320 | Are there plans to m igrate dat a to VA En terprise T ool? | |
321 | If yes, wh en? | |
322 | ||
323 | ||
324 | Documentat ion | |
325 | Management | |
326 | Jazz Proje ct(s): | |
327 | MHLTH (CM) | |
328 | Team Area( s): | |
329 | Clozapine | |
330 | MOD | |
331 | Is it insi de VA fire wall? | |
332 | Physical s erver loca tion: | |
333 | Company/ Bldg/City/ State | |
334 | Server nam e: | |
335 | Contact pe rson for a ccess: | |
336 | Name/Ph one/email | |
337 | Are there plans to m igrate dat a to VA En terprise T ool? | |
338 | If yes, wh en? | |
339 | ||
340 | Build Mana gement | |
341 | Jazz Proje ct(s): | |
342 | MHLTH (CM) | |
343 | Team Area( s): | |
344 | Clozapine Modernizat ion | |
345 | MHLTH_MOD_ CLOZ_MOD_S RC | |
346 | Developmen t is occur ring in Vi sual Studi o and then being upl oaded to R ational | |
347 | ||
348 | Test Manag ement | |
349 | Jazz Proje ct(s): | |
350 | MHLTH (QM) | |
351 | Team Area( s): | |
352 | Clozapine | |
353 | RUCL | |
354 | ||
355 | ||
356 | Requiremen ts Managem ent | |
357 | Jazz Proje ct(s): | |
358 | MHLTH (RM) | |
359 | Team Area( s): | |
360 | Clozapine | |
361 | RUCL | |
362 | ||
363 | ||
364 | ||
365 | Interface/ Dependency Managemen t | |
366 | Projects m ust be awa re of how changes af fect other products. This in teractive nature may occur as an interfa ce or a de pendency. An interf ace is a s hared boun dary throu gh which i nformation is exchan ged; where as a depen dency occu rs when on e product relies on informatio n from ano ther produ ct. This project i nterfaces with or is dependent upon prod ucts liste d in the t able below and will require co ordination between t he teams t o exchange informati on and cod e changes throughout the devel opment lif ecycle. Th is will fa cilitate a smoother release an d minimize risks for each of t he project s. The co nfiguratio n managers from the teams will facilitat e all exch anges to t rack and m anage arti facts ente ring or le aving this project. The table below ide ntifies al l interfac es, depend encies and associate d informat ion: | |
367 | Product Na me / Versi on # | |
368 | Interface (I) or | |
369 | Dependency (D) | |
370 | Project | |
371 | Manager | |
372 | Configurat ion | |
373 | Manager | |
374 | ADD CURREN T VERSION of the Reg istry here for each monthly re port | |
375 | CLOZ_MOD_R EG_0.x.x.x | |
376 | I | |
377 | Kristen Te mplet | |
378 | Ursula Wil son / Terr ance Hardi son | |
379 | ||
380 | CCM Implem entation | |
381 | The Config uration Ma nager will be engage d with the project f rom the pl anning sta ge through to projec t closeout to provid e complete lifecycle support. | |
382 | CCM Enviro nment Plan ning and S etup | |
383 | Configurat ion Manage rs collabo rate with Project Ma nagers to identify t he product s to be mo dified dur ing the de velopment cycle and document t he configu ration ite ms. The C onfigurati on Manager uses this informati on and pre pares the CCM enviro nment by: | |
384 | Identifyin g and obta ining acce ss to the appropriat e CCM repo sitories | |
385 | Requesting an isolat ed area wi thin the C CM reposit ories for project de velopment | |
386 | Submitting access re quests wit h the appr opriate ro les for pr oject team members | |
387 | Creating d evelopment , integrat ion and ba seline str eams as ap propriate | |
388 | Populating the strea ms with th e appropri ate baseli nes to cre ate the fo undation f rom which developmen t will beg in | |
389 | Creating s pecific id entifiers for use in change re cords to u niquely id entify the project a nd any spe cific elem ents withi n the proj ect | |
390 | Collaborat ing with t he Scrum M aster to m ap change records to specific backlogs o r sprint p lans | |
391 | ||
392 | Creating w ork instru ctions to identify p rocesses a nd assist the team i n proper u se of the CCM tools | |
393 | Creating C M Plan | |
394 | Developmen t Support | |
395 | Configurat ion Manage rs work wi th all mem bers of th e project team durin g the deve lopment/pr oject life cycle. The y provide team speci fic traini ng on CCM processes and use of the CCM t ools. The y provide first line CCM tools support. They stay informed o n any CCM tool chang es or main tenance an d keep the team info rmed to mi nimize imp acts on de adlines. T hey also p rovide sup port that is specifi c to certa in roles. | |
396 | Developers : | |
397 | Assist wit h code mer ges betwee n streams | |
398 | Coordinate developer s and CCM tools supp ort to imp lement bui ld tools s uch as Bui ldForge | |
399 | Apply base lines imme diately fo llowing bu ild comple tion | |
400 | Validate a ppropriate change re cord statu s through the use of queries a nd dashboa rds | |
401 | SQA: | |
402 | Identify c hanges bet ween build s to assis t with tes ting scope by follow ing baseli ne process es | |
403 | Assist wit h linking capabiliti es between change re cords, tes t artifact s and requ irements | |
404 | Incorporat e linking validation through u se of quer ies and da shboards | |
405 | Release Pr eparation | |
406 | Configurat ion Manage rs are res ponsible f or packagi ng and doc umenting r eleases: | |
407 | Verify bas elines to identify t he artifac ts that co mprise the release | |
408 | Finalize t he Version Descripti on Documen t that has been cont inuously u pdated wit h each bui ld that wa s promoted outside o f the deve lopment te am’s integ ration tes t environm ent. The V DD now con tains all changes ma de since t he previou s release. | |
409 | Bundle the artifacts and perfo rm the han doff to th e appropri ate partie s | |
410 | Project Cl oseout | |
411 | The Config uration Ma nager will work with the PM to perform t he followi ng tasks p rior to th e end of t he project : | |
412 | Update all change re cords and promote th rough to c ompletion | |
413 | Make sure no artifac ts are che cked out i n source c ontrol | |
414 | Make sure that no ar tifacts ar e locked t o prevent updates in source co ntrol | |
415 | Archive an ything tha t is proje ct specifi c and will not be re used by a future pro ject | |
416 | Request Ja zz access removal or role chan ges for an y team mem bers who w ill no lon ger be wor king on th e project | |
417 | Determine if the dev elopment p roject are a should b e archived | |
418 | Assist tea m members in removin g any work areas use d during t he develop ment proce ss that wi ll not be used in th e future | |
419 | ||
420 | Configurat ion Identi fication | |
421 | This proje ct will ma intain sta ndard nami ng convent ions for a ll CIs cre ated. VA standards that have been ident ified will be follow ed, such a s for end user docum entation a nd MUMPS p atches. W here no VA standards are defin ed, the pr oject will define th e naming c onvention used. | |
422 | Naming Con ventions | |
423 | Artifact T ype | |
424 | Format | |
425 | Comment | |
426 | Main | |
427 | Timeline | |
428 | MHLTH_CLOZ _MOD (Proj ect Timeli ne) | |
429 | Project (P roduct) le vel Main T imeline | |
430 | Additional | |
431 | Timelines | |
432 | NA | |
433 | Timeline a ssociated with Cloza pine Team Area | |
434 | Increment | |
435 | Iterations | |
436 | ||
437 | Build Iter ations (VI P) | |
438 | ||
439 | Sprint Ite rations | |
440 | ||
441 | ||
442 | ||
443 | ||
444 | ||
445 | ||
446 | ||
447 | ||
448 | ||
449 | ||
450 | ||
451 | ||
452 | ||
453 | Sprint Ite rations | |
454 | Continued | |
455 | ||
456 | MHLTH_CLOZ _MOD_Build _1 | |
457 | MHLTH_CLOZ _MOD_Build _2 | |
458 | MHLTH_CLOZ _MOD_Build _3 | |
459 | MHLTH_CLOZ _MOD_Build _4 | |
460 | MHLTH_CLOZ _MOD_Build _5 (option al tasks) | |
461 | MHLTH_CLOZ _MOD_Build _6 (option al tasks) | |
462 | ||
463 | ||
464 | ||
465 | ||
466 | MHLTH_CLOZ _MOD_B1_Sp rint_0 | |
467 | MHLTH_CLOZ _MOD_B1_Sp rint_1 | |
468 | MHLTH_CLOZ _MOD_B1_Sp rint_2 | |
469 | MHLTH_CLOZ _MOD_B1_Sp rint_3 | |
470 | ||
471 | MHLTH_CLOZ _MOD_B2_Sp rint_4 | |
472 | MHLTH_CLOZ _MOD_B2_Sp rint_5 | |
473 | MHLTH_CLOZ _MOD_B2_Sp rint_6 | |
474 | MHLTH_CLOZ _MOD_B2_Sp rint_7 | |
475 | ||
476 | MHLTH_CLOZ _MOD_B3_Sp rint_8 | |
477 | MHLTH_CLOZ _MOD_B3_Sp rint_9 | |
478 | MHLTH_CLOZ _MOD_B3_Sp rint_10 | |
479 | MHLTH_CLOZ _MOD_B3_Sp rint_11 | |
480 | ||
481 | MHLTH_CLOZ _MOD_B4_Sp rint_12 | |
482 | MHLTH_CLOZ _MOD_B4_Sp rint_13 | |
483 | MHLTH_CLOZ _MOD_B4_Sp rint_14 | |
484 | MHLTH_CLOZ _MOD_B4_Sp rint_15 | |
485 | ||
486 | MHLTH_CLOZ _MOD_B5_Sp rint_16 | |
487 | MHLTH_CLOZ _MOD_B5_Sp rint_17 | |
488 | MHLTH_CLOZ _MOD_B5_Sp rint_18 | |
489 | MHLTH_CLOZ _MOD_B5_Sp rint_19 | |
490 | ||
491 | MHLTH_CLOZ _MOD_B6_Sp rint_20 | |
492 | MHLTH_CLOZ _MOD_B6_Sp rint_21 | |
493 | MHLTH_CLOZ _MOD_B6_Sp rint_22 | |
494 | MHLTH_CLOZ _MOD_B6_Sp rint_23 | |
495 | ||
496 | Increment Iterations /Build Ite rations/Sp rint Itera tions were set up in Rational to be in s ync with t he Cloud d evelopment sprints | |
497 | Plans | |
498 | MHLTH_CLOZ _MOD_B2_Sp rint_4 | |
499 | MHLTH_CLOZ _MOD_B2_Sp rint_5 | |
500 | MHLTH_CLOZ _MOD_B2_Sp rint_6 | |
501 | MHLTH_CLOZ _MOD_B2_Sp rint_7 | |
502 | MHLTH_CLOZ _MOD_B2_Sp rint_8 | |
503 | MHLTH_CLOZ _MOD_B2_Sp rint_9 | |
504 | ||
505 | This proje ct does no t involve software d evelopment in the Ra tional Too l. The Re lease Plan is the on ly plan us ed. | |
506 | ||
507 | Artifact T ype | |
508 | Format | |
509 | Comment | |
510 | Documents | |
511 | Clozapine_ MOD_Versio n_Descript ion_Docume nt.docx | |
512 | ||
513 | Release Ca ndidates | |
514 | None at th is time | |
515 | ||
516 | Baselines | |
517 | ||
518 | Update at the end of each Spri nt: | |
519 | MHLTH_CLOZ _MOD_SRC ( *4: MHLTH_ CLOZ_MOD_R EG_0_2_7_4 ) | |
520 | ||
521 | Pull this informatio n from the Eclipse t ool | |
522 | ||
523 | Configurat ion Contro l (Version and Basel ine Manage ment) | |
524 | Source Cod e – N/A fo r Infrastr ucture | |
525 | This proje ct will be modifying artifacts developed in <MUMPS , Java, De lphi, .net , Java Scr ipt, SQL, etc>. | |
526 | While MUMP S developm ent occurs and patch es are cre ated in Vi stA develo pment acco unts, a co py of the MUMPS code will be s tored in t he MUMPS_s rc compone nt within the approp riate VA C fM reposit ories. | |
527 | All non-MU MPS source code will be manage d/controll ed utilizi ng the VA enterprise CfM tools . For new developme nt, the Cf Mgr will c ollaborate with the developers and the E nterprise Tools Team to determ ine the pr oper compo nent struc ture. Mod ifications to an exi sting code base will occur on a developm ent stream populated with the baseline t hat reflec ts the app ropriate s tarting co de base. A ll changes will be a ssociated with a cha nge record that will be used t o apply th e changes back to th e developm ent stream . | |
528 | Documentat ion | |
529 | All projec t related documents will be ma naged/cont rolled usi ng the VA standard d irectory s tructure i n the desi gnated doc ument repo sitory. Al l project documentat ion will a dhere to V A policy o n protecti on of VA s ecurity an d VA archi tecture co ntent, des ensitizati on of pati ent data c ontent, FO IA content redaction restricti ons, 508 a ccessibili ty standar ds, and do cumentatio n standard s where ap plicable. The CM_Do c_Map will be used t o determin e the loca tion of ea ch documen t within t he directo ry structu re. | |
530 | ||
531 | Environmen t – N/A fo r Infrastr ucture | |
532 | The projec t will uti lize a num ber of ser vers for d evelopment , testing and user a cceptance tests (UAT ). While MUMPS deve lopment oc curs withi n a VistA account, d evelopment of non-MU MPS patche s will occ ur on the developers ’ machine and underg o initial testing on ce deploye d to a ser ver. | |
533 | Clozapine Environmen ts – N/A | |
534 | Developmen t | |
535 | SQA | |
536 | UAT | |
537 | N/A | |
538 | N/A | |
539 | N/A | |
540 | The develo pment envi ronments w ill be kep t up-to-da te with na tionally r eleased pa tches but will other wise be an uncontrol led enviro nment. Thi s allows d evelopers maximum fl exibility. | |
541 | The SQA an d UAT envi ronments w ill be rig orously co nfiguratio n controll ed to ensu re that te sting occu rs against known bas elines. T he environ ments will be update d routinel y with nat ionally re leased pat ches, and all patche s loaded i nto the en vironment( s) that ar e still un der develo pment will be record ed as part of the ba seline. | |
542 | Change Man agement | |
543 | Story and Task Manag ement | |
544 | This proje ct will us e the agil e methodol ogy to man age the de velopment lifecycle. As such, change ma nagement w ill be acc omplished through ag ile practi ces and ce remonies: | |
545 | Product Ow ner define s, approve s and prio ritizes re quirements | |
546 | Scrum Team collabora tes with P roduct Own er for req uirements elaboratio n | |
547 | Detailed r equirement s are defi ned as Sto ries and p laced into a Product Backlog ( Backlog Gr ooming) | |
548 | The Scrum Master lea ds sprint planning s essions wi th Scrum T eam to det ermine sco pe for upc oming spri nt, storie s are sele cted and m oved into the Sprint Plan | |
549 | Scrum Team creates t asks linke d to the s tories to define the work to b e accompli shed durin g the spri nt | |
550 | End of spr int ceremo nies revie w with the Product O wner what was accomp lished | |
551 | Planning f or next sp rint occur s | |
552 | Consistent with agil e, require ments can change, be refined o r repriori tized by t he Product Owner at any time. The Produ ct Owner m ust approv e any chan ges initia ted by the Scrum Tea m. | |
553 | Defect Man agement | |
554 | Defects ar e logged a nd linked to their a ssociated requiremen t and to t he test ca se verifyi ng the fix . Defects can be ide ntified an d logged b y anyone. New defec ts will be reviewed during the Scrum mee ting. If a defect c rashes the system or prevents testing fr om proceed ing, it wi ll be assi gned a sev erity 1 or 2 and wil l be repai red immedi ately. If the defect repair af fects the team’s abi lity to co mplete sch eduled wor k for the sprint, th e Product Owner will be consul ted. A de cision wil l be made to either prolong th e sprint o r move unf inished wo rk to a fu ture sprin t. Non-cri tical defe cts will b e placed i n the back log and sc heduled fo r repair i n a future sprint. | |
555 | Risk/Issue Managemen t | |
556 | VA’s Enter prise Risk Managemen t Office ( ERMO) defi nes the pr ocesses fo r risk and issue man agement. I nformation can be fo und in the Process A sset Libra ry (PAL) w ithin the Quality, P rivacy and Risk Fram ework. VA ’s enterpr ise change and confi guration m anagement tool will be used to log and m anage issu es and ris ks. Issues that requ ire change s to the p roduct wil l be logge d and trac ked as tas ks. | |
557 | ||
558 | Status Acc ounting | |
559 | This proje ct will us e the VA e nterprise CCM tool’s query, re port and d ashboard f unctionali ty for sta tus accoun ting. | |
560 | Dashboards | |
561 | The VA ent erprise CC M tool con tains nume rous widge ts to refl ect the st atus of re quirements , developm ent and te sting. Th is project will leve rage those capabilit ies to pro vide real- time data on Risk, I ssue, Stor y, Task an d Defect s tatus; spr int progre ss; worklo ad; projec t burn up and burn d own; and t esting sta tus. The d ashboard w ill be vis ible to an yone liste d as a mem ber of the developme nt project ’s team ar ea. | |
562 | Queries | |
563 | The config uration ma nager will create a set of sha red querie s to extra ct data to be export ed to a sp readsheet and shared outside o f the CCM tool. The queries w ill provid e summary informatio n on stori es, tasks, defects, issues and risks. A CfMgr can run queri es at regu lar interv als and pr ovide resu lts to man agement on a routine basis. | |
564 | Name of Sh ared Query | |
565 | Purpose | |
566 | Create que ries as ne eded or re quested | |
567 | As needed. | |
568 | ||
569 | General St atus Repor ts | |
570 | Based on p roject nee d, reports are gener ated out o f the VA e nterprise CCM tool. Standard report tem plates wer e created by the too ls support team and will be le veraged as necessary . New rep orts are c reated if existing t emplates d o not sati sfy the pr oject’s ne eds. | |
571 | Name of Re port | |
572 | Purpose | |
573 | Reports cr eated as n eeded. | |
574 | ||
575 | ||
576 | ||
577 | Configurat ion Audits and Revie ws | |
578 | This proje ct will pe rform audi ts and rev iews to en sure the i ntegrity o f the prod uct throug hout the d evelopment process. Such audi ts and rev iews will vary in co mplexity a nd formali ty. | |
579 | Audit/Revi ew Type | |
580 | Descriptio n | |
581 | Purpose | |
582 | Performed By | |
583 | Frequency | |
584 | VDD | |
585 | Content re view | |
586 | Verify fun ctionality | |
587 | Dev Mgr | |
588 | Each relea se | |
589 | VDD | |
590 | Validate a gainst dat a in CCM t ool | |
591 | Verify acc uracy | |
592 | CfMgr | |
593 | Each relea se | |
594 | Build – N/ A for Infr astructure | |
595 | Validate p lanned cha nges are r eflected i n baseline | |
596 | Verify bas eline inte grity | |
597 | CfMgr | |
598 | Each build to be pro moted to S QA | |
599 | SQA Enviro nment – N/ A for Infr astructure | |
600 | *Document last time nationally released patches we re applied to enviro nment | |
601 | *Identify test patch es by test version | |
602 | *Cite any unique con figuration settings required | |
603 | Verify con figuration and basel ine agains t which te sting will occur | |
604 | SQA Mgr | |
605 | Each time the baseli ne changes | |
606 | ||
607 | Release Ma nagement | |
608 | Release Ma nagement w ithin CCM maps to De velopment Build Prom otion Mana gement as to not be confused w ith OIT Re lease Mana gement. A release i s defined as the gro uping of o bjects phy sical or e lectronic along with all the s upporting media (doc umentation ) necessar y to satis fy a given set of re quirements . | |
609 | This proje ct will cr eate relea se package s for a va riety of r easons thr oughout th e developm ent lifecy cle. Altho ugh they a re release packages that will be promote d, these p ackages wi ll not be official R eleases un til OIT Re lease Mana gement has verified the packag e has been placed in to product ion. OIT Release Ma nagement d etermines the method s of packa ging and t he rules c oncerning management of a rele ase. | |
610 | Electronic Release P ackage – N /A for Inf rastructur e | |
611 | The electr onic relea se package will cont ain execut able(s), i nstallatio n scripts, user guid e, install ation docu mentation, and any r equired su pporting s oftware on electroni c media. T he executa ble is gen erated fro m a baseli ne. The el ectronic p roduction release pa ckage medi a will be labeled wi th an iden tification number, d escriptive name, and release d ate. A sof t copy of the VDD wi ll be gene rated and sent with the electr onic produ ct as part of the re lease pack age. | |
612 | Version De scription Document | |
613 | The Versio n Descript ion Docume nt (VDD) d escribes t he documen tation, me dia used i n producin g the deli verable, a nd the con tents of t he release package ( both physi cal and fu nctional). The VDD w ill be pro duced when the first build is promoted t o the firs t testing environmen t outside of the dev elopment t eam’s inte gration te st environ ment and m odified wi th each pr omotion to other env ironments. This pro ject will use the la test VA ap proved VDD template. | |
614 | Training | |
615 | Access to the CCM to olset requ ires compl etion of t raining wi thin TMS. All proje ct team me mbers will complete the requir ed trainin g prior to requestin g access. Any subseq uent train ing will b e conducte d / facili tated by t he Project Manager, Developmen t Manager and or the CCM Team for each V A product. | |
616 | CCM Backup and Disas ter Recove ry Plans | |
617 | Data store d in the V A enterpri se CCM too ls are bac ked up on a regular basis. The servers a re located in the Hi nes datace nter, and the VA Rat ional Tool s Team mon itors and manages th e backups. This pro ject team will ensur e that its data is b acked up b y checking artifacts into the tool daily and updat ing work i tems consi stently. Any need t o restore data will be coordin ated with the VA Rat ional Tool s Team. As an additi onal metho d of recov ery, this project wi ll apply b aselines a nd snapsho ts at freq uent inter vals to pr ovide a mo re easily accessible restore p oint. | |
618 | ||
619 | ||
620 | ||
621 | ||
622 | ||
623 | ||
624 | Template R evision Hi story | |
625 | Date | |
626 | Version | |
627 | Descriptio n | |
628 | Author | |
629 | May 2017 | |
630 | 2.7 | |
631 | Rewritten to make co ncise and address CC M within t he Agile m ethodology | |
632 | EPMO_CCMO | |
633 | November 2 012 | |
634 | 2.6 | |
635 | Additional updates t o current guidelines for Secti on 508 con formance | |
636 | Process Ma nagement | |
637 | August 201 2 | |
638 | 2.5 | |
639 | Additional updates f or Section 508 confo rmance | |
640 | Process Ma nagement | |
641 | June 2012 | |
642 | 2.4 | |
643 | Updated to current P roPath doc umentation standards and edite d for Sect ion 508 co nformance | |
644 | Process Ma nagement | |
645 | May 2012 | |
646 | 2.3 | |
647 | Corrected numbering formatting for parag raph 5.1.2 and later paragraph s, and upd ated Table of Conten ts and doc ument vers ion/date f rom 2.2/ J une 13, 20 11 to 2.3 / May 23, 2012 | |
648 | Process Ma nagement | |
649 | June 2011 | |
650 | 0.4 | |
651 | Updated pe r ProPath meeting fo r Change, Configurat ion, and R elease Man agement th e week of May 16th, 2011 | |
652 | Process Ma nagement | |
653 | January 20 11 | |
654 | 0.3 | |
655 | Updated Ro le and Res ponsibilit ies table | |
656 | SCM Commit tee | |
657 | August 200 9 | |
658 | 0.2 | |
659 | Draft – SC M Committe e Updates | |
660 | SCM Commit tee | |
661 | June 2009 | |
662 | 0.1 | |
663 | Draft – SC M Committe e Updates | |
664 | SCM Commit tee | |
665 |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.