WPID F1.

1-M Lessons Learned /

Retrospective

Projects Information
Project ID: PG193 (121674) Project Name: Sales FMO AVPN Ph1
Project Install date: 06/14/2009 Project WBS:
Organization: Program: FMO
Life Cycle Phase:
Attendees or Contributors Name Area of Representation
Bob Mayo ETE PM

Project ID: PG195 (121655) Project Name: Sales FMO New Functionality
Project Install date: 06/14/2009 Project WBS:
Organization: Program: FMO
Life Cycle Phase:
Attendees or Contributors Name Area of Representation
Sanju Thomas ETE PM

Project ID: PG196 (121656) Project Name: Sales FMO MIS-AKPRVIHI Ethernet T
Project Install date: 06/14/2009 Project WBS:
Organization: Program: FMO
Life Cycle Phase:
Attendees or Contributors Name Area of Representation
Aram Kratlian ETE PM

Project ID: PG198 (121680) Project Name: Sales FMO MIS MACD
Project Install date: 06/14/2009 Project WBS:
Organization: Program: FMO
Life Cycle Phase:

PPA-IUP-WBTM-25 Proprietary Information Page 1 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Attendees or Contributors Name Area of Representation

Sreenatha Gaddalay ETE PM

Project ID: PG199 (121673) Project Name: Sales FMO Fallout Defects
Project Install date: 06/14/2009 Project WBS:
Organization: Program: FMO
Life Cycle Phase:
Attendees or Contributors Name Area of Representation
Pramod Duttargi ETE PM

Project ID: PD511 (117899) Project Name: Global Managed Services Part1
Project Install date: 06/14/2009 Project WBS:
Organization: Program: FMO
Life Cycle Phase:
Attendees or Contributors Name Area of Representation
Myrna Cadelina ETE PM

Project ID: 117899f Project Name: DUNS Matching for Global Managed Services Part 1
Project Install date: 06/14/2009 Project WBS:
Organization: Program: FMO
Life Cycle Phase:
Attendees or Contributors Name Area of Representation
Savita Rajeevlochan ETE PM

PPA-IUP-WBTM-25 Proprietary Information Page 2 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Project Evaluation and Accomplishments

PG193:

PG193 did not complete all phases of testing prior to release. AT&T gave the approval to proceed to delivery and was
delivered to production successfully on the scheduled date. UCT was a ‘Go’ with no outstanding issues on UCT day.
Testing was completed through ABR processing during the release and then through SOR on the Monday after release.
After completion, the test case was cancelled

PG195:
This project is important to ATT business to make sure that users are led down an intuitive and easy path to generate
quotes, contracts and orders
 Customers are able to electronically sign contract documents
 Authorized AT&T resources are able to electronically countersign contract documents
 Sales not required to re-key data that has already been entered in other systems
 Users are able to generate standard reports and create ad hoc reports/ad hoc queries without engaging IT /
Labs
 Administrators are able to maintain and configure templates without engaging IT/Labs
 Minimal training required for sales and support

PG196:
This project delivered two main deliverables: 1) Support for MIS in Alaska, Hawaii, Virgin Islands and Hawaii, including
MACD, across the FMO platform. 2) Domestic Ethernet for MIS. It was approved for installation by AT&T and IBM release
management and was successfully implemented on 6/14. However, JST and UAT did not complete but will continue testing
through the end of June. This is with the full support and approval of AT&T FMO.

PG198:

PG199:

PD511:
PPA-IUP-WBTM-25 Proprietary Information Page 3 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

117899f:

Estimating and Planning Resources Evaluation

Required for ALL Projects:

PG193 :

Planned Delivery Actual Delivery Planned Actual Hours or

Date Date Hours or FTP FTP (through
6/19/09)

Project Level 06/14/2009 06/14/2009 131.87 ftps 139.41 ftps

Reason for Variance Variance is within limits. Less than the +/- 20% variance
outside +/- 20 for Large
Projects (Greater than 3
FTPs) and +/-30% for
Small Projects (Less
than 3 FTPs) of
organization objective."

PG195:

PPA-IUP-WBTM-25 Proprietary Information Page 4 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Planned Delivery Actual Delivery Planned Actual Hours or

Date Date Hours or FTP FTP

Project Level 06/14/2009 06/14/2009 82.51 ftps 80.67 ftps

Reason for Variance Variance is within limits. Less than the +/- 20% variance
outside +/- 20 for Large
Projects (Greater than 3
FTPs) and +/-30% for
Small Projects (Less
than 3 FTPs) of
organization objective."

PG196 :

Planned Delivery Actual Delivery Planned Actual Hours or

Date Date Hours or FTP FTP (through
6/19/09)

Project Level 06/14/2009 06/14/2009 199.92 ftps 188.28 ftps

Reason for Variance Variance is within limits. Less than the +/- 20% variance
outside +/- 20 for Large
Projects (Greater than 3
FTPs) and +/-30% for
Small Projects (Less
than 3 FTPs) of
organization objective."

PG198 :

PPA-IUP-WBTM-25 Proprietary Information Page 5 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Planned Delivery Actual Delivery Planned Actual Hours or

Date Date Hours or FTP FTP (through
6/19/09)

Project Level 06/14/2009 06/14/2009 151.28 ftps 164.41 ftps

Reason for Variance Variance is within limits. Less than the +/- 20% variance
outside +/- 20 for Large
Projects (Greater than 3
FTPs) and +/-30% for
Small Projects (Less
than 3 FTPs) of
organization objective."

PG199 :

Planned Delivery Actual Delivery Planned Actual Hours or

Date Date Hours or FTP FTP (through
6/19/09)

Project Level 06/14/2009 06/14/2009 41.58 ftps 39.33 ftps

Reason for Variance Variance is within limits. Less than the +/- 20% variance
outside +/- 20 for Large
Projects (Greater than 3
FTPs) and +/-30% for
Small Projects (Less
than 3 FTPs) of
organization objective."

PD511 :

PPA-IUP-WBTM-25 Proprietary Information Page 6 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Planned Delivery Actual Delivery Planned Actual Hours or

Date Date Hours or FTP FTP (through
6/19/09)

Project Level 06/14/2009 06/14/2009 121.46 ftps 110.78 ftps

Reason for Variance Variance is within limits. Less than the +/- 20% variance
outside +/- 20 for Large
Projects (Greater than 3
FTPs) and +/-30% for
Small Projects (Less
than 3 FTPs) of
organization objective."

117899f :

Planned Delivery Actual Delivery Planned Actual Hours or

Date Date Hours or FTP FTP (through
6/19/09)

Project Level 06/14/2009 06/14/2009 1.09 ftps 1.12 ftps

Reason for Variance Variance is within limits. Less than the +/- 20% variance
outside +/- 20 for Large
Projects (Greater than 3
FTPs) and +/-30% for
Small Projects (Less
than 3 FTPs) of
organization objective."

PPA-IUP-WBTM-25 Proprietary Information Page 7 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Quality Results Evaluation

PG193 :

CR Summary
CR011 AVPN Integrated Services- ETE-PE140, PE141, PE139, and PF035
CR026 AVPN Updates
CR056 EFMS-PM Updates
CR087 EFMS-PM Web service Update
CR095 AVPN Service Availability
CR129 setProjectPackage to Support RDS
CR266 Remove Vendor Sold Notice Requirements for JRD and swBRD for PG193. This is
a documentation only change to align the JRD and swBRD with the agreements made and
implementation moving forward
CR271 Make changes to the generateActivityGroupReport() web services on the request
and response blocks. eCRM has a need to query based on MDS ID to return all of child Activity
Group Reports for the MDS ID.
CR308 Update is required to the AVPN Pricing Schedule.
CR312 Missing PG193 AVPN RDS fields that need to be captured by ADOPT and GCP.
CR313 Collecting an AVPN discount for the Sub-Categories levels.
CR379 ECRM HLD Updates
CR380 ICT & CMT Data WSDL Update
CR394 Support Requests-Remove BCS Specifics from ADOPT
CR404 eCRM code change for CustomerID”.
CR428 Make BillingAddress and Contact
blocks optional for setBillAccountPackage and getBillAccountPackage. Fixing R209 JST QC-
11828 Ticket

SQA Summary An SQA audit was conducted in the R&F & Design phases – Passed.

Release Management Project was released through Release Management and was successfully
deployed on 6/14/09.
Test Summary All features were ST to completion. JST test was conducted and to be
completed post release. UAT did not complete prior to the June release and
then continued post release. ATT gave the go to continue to UCT in the July
Release. CRs313 and CR381 were deferred to project 121680a for the July
release
ITO - Information
Technology Operations
(includes Managed
PPA-IUP-WBTM-25 Proprietary Information Page 8 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Operations / PSO as
applicable)
E-Governance
as applicable

PG195

CR Summary
CR033 Custom Pricing CR
•DBOR in custom pricing process for Solution XML should return the Solution URL to
eCRM. DBOR should not be processing spreadsheet
CR126 Custom Pricing SD Update
•SFD Document update to reflect the following changes: the preconditions to
"ReadyForContractGeneration" needs to be stated and clarified, the hierarchy of the
price types (i.e. budgetary, icb, firm) needs to be stated as well, for the Resubmit - we'll
be reusing the same pricing scenario as in the original request
CR223 A new MIS Pricing Schedule (PS) to support SEU and SEUL Single Site promotions with
MLPPP is being provided for the R209 release (unsure which project this will fall into).
This template simply adds verbiage to support a single site using the standard MIS PS.
CR227 Whenever a MSA/UA is generated, the letters “UA” need to be appended to the system-
generated AT&T MA Reference No.
CR257 For code impact – there is a need, due to other PG195 requirements, to update eCRM
WSDLs.
This may impact:ABN on the Web (BeSales),eGBS,eSIGN,IMS2,SalesOne, IGLOO.
CR263 Use BGW as a gateway between GCP and CADM for CADM real-time data. GCP will
need a web service interface with BGW to retrieve the CADM data required for the
getContractInventoryDetails, getContractInventorySummary and getBillAccountList web
services.
CR291 ADOPT has to implement Express Orders for the R109 February 2009 Release.
Cover additional scenarios when COS is YES for Basic offers and No for Plus (managed
offers) of express hadling
For TOI Derivation rules, please refer to the “TOI Derivation - OI_AD_AJ_01072009.xls”
Excel file.
CR292 In eSign, instead of giving the user (AE) a backend process to generate the custom
language support request, client is requesting to be able to launch from eSign to eCRM
to create the custom language support request that is currently in use today.
CR293 CTS Performance Testing requested to measure the response time of key transactions
in eCON, review with the users and tune the application as needed prior to the R209
release in June.
CR299 IMS2 Credit Element
OPS/ADOPT will read the pricing results (discounts, rates, credits, etc.) of the custom
pricing activities and present those results to sales
CR315 The proposal for change provides:
PPA-IUP-WBTM-25 Proprietary Information Page 9 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

a) eCON to send eSign the selected ODM information for a contract negotiation at the
contract group level.
b) eSign will display this information on the Deliver Contracts screen.
CR316 Restart/Error Recovery was not in the original scope.
i. Application (eCRM, ADOPT, eCON, eSign) will trap the error at the point of failure in
the Contract Negotiation flows (Move, Remove, Update, Custom Language) and report
to C-BUS.
CR321 In order to maintain availability for FMO, a snapshot copy of CADM will be created.
Ordering activity will continue using the snapshot, while billing initiation activity takes
place on the original copy of the data
CR322 COBRA Biller Code Block
Ensure MIS/BVOIP account setups are not done using COBRA biller triplets.
CR326 Needed to support SE&A Activities for the design checkpoint/CDR (produces the data
flow diagrams (DFDs), test plan reviews, test sets reviews, Root Cause Analysis) during
JST and UAT.
CR338 Create a new tab on the eSign Customer List call “Archive”. The AE would be given
control on all other tabs where eSign requests exist to select one or more eSign requests
and move them to an Archive Tab and the ability to move the request(s) back to the
appropriate status.
CR346 BGW needs to provide the PHI instead of Component ID when providing the IDs for
plans and charges.
This includes Pricing Plan, Contract, Discount, Rate Plan and Inventory items as
specified on the queries from project PG195 and PG198. BGW will need to derive these
IDs for plans using the SA FBO table and existing logic used for other projects.
CR347 ADOPT has identified the following 4 Documentation Only updates that need to be made
to the ADOPT HLD & AID.
1. HLD -label name changes
2. AID - ADOPT Contract Negotiation to remove the error-codes
3. HLD-3.1.2: Change the HLD Requirement Description.
4. ADOPT-CBUS AID for PricingScenarioStatus Event & ToDoActivity Event.
CR359 GCP PricingScenario IAD update for the change from
<AssociatedCustomerLocationXref> to <AssociatedCustomerSiteXref>
CR376 SRD changes for PG195 ECRM SRD to -
• SetOpty Clarifications
• Todo Delete Button Added
• Removed Assigned to in Emails for ToDo
• ICB SR - Rules on how to refresh the records
• Review Board/ Capacity Check Clarifications on Approval Effective Date
CR402 eCRM changes from PG195 Demo
CR410 This PG195 CR is for GCP to cleanup DPPCO records to prevent duplicates when
ADOPT writes same product component data into GCP at different times
CR413 This CR is for the following changes to be made to eCRM and eCON. (These changes
were made during the design phase. This is a documentation CR to update the swBRD
to match the design & coding)
CR441 eSign Full Browser Window

PPA-IUP-WBTM-25 Proprietary Information Page 10 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

SQA Summary An SQA audit was conducted in the R&F & Design phases – Passed with no
Non Conformances or Non Compliances.

Release Management Project was released through Release Management and was successfully
deployed on 6/14/09.
Test Summary All features were STed and JSTed to completion. UAT did not complete prior
to the June release and then continued post release.
ITO - Information
Technology Operations
(includes Managed
Operations / PSO as
applicable)
E-Governance
as applicable

PG196

CR Summary
CR372 Update HLD requirements to reflect changes suggested by development team
during coding.
CR373 Add DSM-FEDI as test support only.
CR258 Add GIOM and EFMS to project to reflect feature changes to HI, AK, PR, VI

SQA Summary An SQA audit was conducted in the R&F & Design phases – Passed.

Release Management Project was released through Release Management and was successfully
deployed on 6/14/09.
Test Summary
All features were ST except for two test cases involving GIOM and eCRM. The
root cause of not completing was in inability to secure test data from ADOPT.
Testing will continue post-implementation with an expected close date of 6/30..
JST test was conducted and completed except for two test cases. One
involves defect 13398 which will require the origination of a CR (478) to be
addressed in Project 121680a. The other involves testing with HSAT (ATT

PPA-IUP-WBTM-25 Proprietary Information Page 11 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

application) which is planned to test through the end of June. If it does not
complete, then a CR will be initiated to also continue processing in 121680a.
UAT did not complete prior to the June release and then continued post
release. ATT gave the go to continue to UCT in the July Release.

ITO - Information
Technology Operations
(includes Managed
Operations / PSO as
applicable)
E-Governance
as applicable

PG198

CR Summary
CR018 PB732 Impacts
•MIS Replacements and A&BR/Contract Automation - it was uncovered late during
Phase 2 timeframe that there is a project targeted for June (PB732) which automates
some additional contracting areas for MIS.
CR047 A&BR Term Length on Renewals
•This CR is being defined to address an identified issue with the current A&BR
implementation of MIS renewal contracts. Currently, in GCSM, a contract to simply
extend the MIS contract for the same term length (eg. 1 year to new 1 year, 2 year to
new 2 year, etc.) without any other contract changes is handled as a
"renewal/addendum".
CR105 ADOPT-eCRM Updates
•During the Design phase discrepancies were found in the ADOPT and eCRM
requirements that require swBRD updates. These changes are documentation-only
updates to maintain consistency between the swBRD and SRDs.
CR193 GIOM MDS ID
•GIOM needs to store the MDS ID (ForeginSorId) retrieved on getActivityGroupPackage
for the BVOIP order, display MDS ID on Order Details Windows, link shopping cart
orders to MDS ID, and allow searches based on MDS ID.
CR242 CADM Impact for MIS MACD
CADM was originally listed as test-only impact. CADM is a critical path for MIS MACD in
retrieving the contract inventory details and is code impacted.
CR248 Data length from upstream application (eCRM) is not matching GIOM data lengths.
GIOM's data lengths match SOR downstream application data lengths.
CR263 Use BGW as a gateway between GCP and CADM for CADM real-time data. GCP will
need a web service I nterface with BGW to retrieve the CADM data required for

PPA-IUP-WBTM-25 Proprietary Information Page 12 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

the getContractInventoryDetails, getContractInventorySummary and getBillAccountList

web services.
CR270 1) In order for ADOPT to receive a set of MIS inventory locations based on a
contract/service triplet first, GCP to create a new synchronous (real-time) MIS
getServiceInventorySummary web services.
2) INSTAR was originally listed as test-only impact but INSTAR data analysis is a critical
path for MIS MACD in retrieving the MIS inventory details.
CR279 Remove following requirement from JRD and swBRD from the scope of project PG198:
B-4.1.2.27: Lifecycle Ordering for MIS/PNT IPTO Contracts.
CR319 Current design allows users to select multiple contracts in eCRM ALP screens. Since
this data is transferred over to ADOPT when the user is launched into ADOPT, eCRM
will limit this transaction to 10 contracts for replacement purposes
CR351 1) rerun the PF703 Clarify and USRP scripts to populate the EFMS generated orders
inputted after the initial PF703 was implemented, and
2) allow Clarify to issue billing disconnects on EFMS generated order
CR392 MACD Functionality - requested scope changes to PG198 MACD functionality.
(Scope reduction)

SQA Summary An SQA audit was conducted in the R&F & Design phases – Passed with no
Non Conformances or Non Compliances.

Release Management Project was released through Release Management and was successfully
deployed on 6/14/09.
Test Summary As a ADOPT was upstream system and most of MACD functionality from
ADOPT was not ready until code deploy, so ST was completed on simulated
data. Extended UAT and PDUAT was carried in 121680a

ITO - Information
Technology Operations
(includes Managed
Operations / PSO as
applicable)
E-Governance
as applicable

PG199
PPA-IUP-WBTM-25 Proprietary Information Page 13 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

CR Summary CR246 GCP code impact from eCRM work for TR-2008-06-1006 and BR-2008-06-1011
CR264b Fallout - Defect # 8127
As a result of accommodating navigation and approval options, ADOPT and eCRM need
to share the same SR status, as well as option approval and expiration detail.
CR277 Impacted organizations, systems, etc.:
MIM Code to generate user files from CENET Data feeds to eCON and ADOPT
CR296 This CR is required to reduce cycle time delays & eliminate SOR defects & manual
handoffs due to missing site level information.
CR340 BDM Discount Restore
Re-instating the BDM envelope with up to 100% discount authority due to a requirements
misinterpretation.
CR348b Defects 9781, 9782_BO Report Fixes
CR349 Defect 8950 and 9073 eCRM dashboard changes
CR350 DEFECT 10046 – 'PF035-TC29 Customer Name Field delete, Account ID field
move
CR353 Defect ID : 11147 i. PE141 - eCRM BO Report Common tab - missing remarks field.
There is no place to enter Project Level notes in ADOPT. There is no Project level notes
entered in eCRM.
CR354 AOTS 113191696: Contract Type on "pseudo" contracts not populating on BO report.
eCon to pass the contract type to GCP for IPT contracts, (including “pseudo” contracts) .
The data element is already in the interfaces.
CR363 DEFECT 9465 – TC25 - Stare and Compare flag is not set when ADOPT SDA
discounting is applied in ADOPT
CR384 Defects 113326735, 10958, 11198, 7342, 8556, 10047 and 10574
CR388 Required for ASAP DPP to maintain parity with PMO.
ASAP DPP needs to increase the number of sites permitted in IPTO MIS, IPTO MIS with
Managed Router, IPTO PNT, and IPTO IPFR deal types.
CR389 Sales Stage and Num of Physical Locs
1. Capture the sales stage of Opportunity at the time of SOR creation.
2. For New ABN, capture ‘# of Physical Locations’ at service type level also.
CR391 GCP OLAP impact from Emptoris 7.5 Update that will impact code for PF701
(March 09 release).
CR393 MARO Fixes.
1. Update ADOPT Order Solution screens for MARO to emulate current Design screens
and functionality.
2. Update ADOPT MARO templates to correct configuration rules. QC Defect 8688.
CR400 This CR will handle the issue where the BO Reports are not being locked in FMO as they
are in the current PMO implementation

SQA Summary

Release Management

PPA-IUP-WBTM-25 Proprietary Information Page 14 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Test Summary

ITO - Information
Technology Operations
(includes Managed
Operations / PSO as
applicable)
E-Governance
as applicable

PD511

CR Summary
Cr 63 UAT Defect 14324
CR 56 CR 56 - ASOC & GCP changes; reverses ASOC WSDL code for base
project
CR 58 CR 58 - IES Descope

SQA Summary

Release Management

Test Summary

ITO - Information
Technology Operations
(includes Managed
Operations / PSO as
applicable)
E-Governance
as applicable

PPA-IUP-WBTM-25 Proprietary Information Page 15 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

117899f

CR Summary

SQA Summary

Release Management

Test Summary

ITO - Information
Technology Operations
(includes Managed
Operations / PSO as
applicable)
E-Governance
as applicable

PPA-IUP-WBTM-25 Proprietary Information Page 16 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

5. Lessons Learned by Phases

Phase 1

What
Worked

Issue Reference Root Cause Resolution Description Key Learnings Candidate for
LL-DB

What Didn’t
Work

Issue Reference Root Cause Resolution Description Key Learnings Candidate for
LL-DB
PG193/PG196/ swBRD was delayed Delay in swBRD caused a We were in a position
PG195/PG198: ripple effect through out the where there was little we
Phase 1 rushed entire schedule causing much could do but try to get
churn to the project. resolutions

PPA-IUP-WBTM-25 Proprietary Information Page 17 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Phase 2

What
Worked

Issue Reference Root Cause Resolution Description Key Learnings Candidate for
LL-DB
PG193/PG196/ Good partnership Good working relationship Continue to partner with
PG195/PG198 with ATT PM ATT PM and work
: P2 Partnering together
PG193/PG196/ Good communication Numerous meeting were held Issue were resolved in
PG195/PG198 to go over issues meeting much more
: P2 quickly than numerous
Communications emails
ALL: P2 Status Joint IBM / ATT meetings Weeking meetings held Continue to work closely
jointly with ATT to discuss all with ATT at a Program
R209 Project status level

What Didn’t
Work

Issue Reference Root Cause Resolution Description Key Learnings Candidate for
LL-DB
PG193/PG196/ Late requirements Delay in swBRD caused a We were in a position

PPA-IUP-WBTM-25 Proprietary Information Page 18 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

PG198 : P2 – ripple effect through out the where there was little we
Constant Churn entire schedule causing much could do but try to get
churn to the project. resolutions
PG193/PG196/ Difficult time getting ATT Required many follow emails, Engage AT&T PM to get
PG198: P2 – Tier1 to baseline HLD Q Messages and meetings to the AT&T votes
Document documents get the necessary approvals
baselining delays
PG196: Project PG196 experienced 3 Required constant coaching Ask AT&T to minimize
Mgmt different AT&T project and training and extra work switching off project
managers throughout to orient the new ATT project managers throughout the
various phases of the manager which took away project lifecycle.
project. Each had a time from actually managing
different style and the project. Once the third
expectation and we lost PM was assigned, some
project momentum at time. stability returned

PPA-IUP-WBTM-25 Proprietary Information Page 19 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Phase 3

What
Worked

Issue Reference Root Cause Resolution Description Key Learnings Candidate for
LL-DB
PG193/PG195/ Need elevated support for Good support from App Establish good
PG198 : P3 App this time crunched project teams to meet schedules. communication with App
Support teams
PG193/PG196/ Issue or questions that Application teams became Engage the Apps and help
PG195 : Issue surfaced were aggressively more efficient at giving them to understand the
Resolution resolved. weekly status. Customer desires for
status

What Didn’t
Work

Issue Reference Root Cause Resolution Description Key Learnings Candidate for
LL-DB
PG193/PG196/ Compressed Schedule Due to the compressed We were in a position
PG195/PG198 schedule of this project and where there was little we
: P3 – Constant the numerous CRs, dates could do but try to get
Churn were often missed and re- resolutions

PPA-IUP-WBTM-25 Proprietary Information Page 20 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

negotiated. Testing was

extremely compressed with
little chance of completing

PG193/PG195 Many CRs causing lots of Getting CRs created in PRISM

: P3 – PRISM schedule churn and getting estimates
CRs/Est
PG196: App Most application failed to be Escalated to 1st and 2nd line Ensure teams know what
Support responsive in providing audit managers and discussed at is expected from them
documentation on a timely executive meetings. and when for audit
basis. Some artifacts, artifacts. Escalate
labeled baselined were, in sooner.
fact, not baselined.

Phase 4

What
Worked

Issue Reference Root Cause Resolution Description Key Learnings Candidate for
LL-DB
PG193/PG196/ ST was managed by Project ST was managed by Project Ensure Project and
PG198: P4 ST Test Manager and Program Test Managers Program test Managers
Completion are engaged early in the
project
PG193/PG196/ UCT on Release Sunday UCT was managed by ATT Continue to work with
PG195/PG198: and they were quick to get ATT to provide them the
P4 – UCT the appropriate support team contacts for UCT.
to the call and get issues
resolved

PPA-IUP-WBTM-25 Proprietary Information Page 21 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

What Didn’t
Work

Issue Reference Root Cause
PG193/PG196/ JST did not complete
PG198 : P4 UCT
PG193/PG195 UCT ran several hours over
: P4 UCT schedule due to late start
with GCP.
PG193: P4 UCT User ID not properly set up
PG196: P4 UCT Project test manager was
not involved enough across
all testing environments.
Many testing issues were
brought to the attention of
the ETE PM to address that
normally would have been
handled by the project test
mgr.
PPA-IUP-WBTM-25
Resolution Description
Due to compressed schedule
and ADOPT completion
issues, JST was unable to
complete testing prior to
release
Had a communication gap
with GCP and their status
The test case had to be
restarted after several hours
of processing due to the
improper set up of the User’s
ID
Set expectations on roles and
responsibilities on future
projects.
Proprietary Information
Key Learnings Candidate for
LL-DB
GCP needs to be better
prepared with their status
communication to ensure
all projects are notified.
AT&T UCT testers need to
understand the test cases
and proactively have all
user id properly set up.
Get clarity on roles at
project inception.
Page 22 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

Phase 5 - Project Closeout

What
Worked

Issue Reference Root Cause Resolution Description Key Learnings Candidate for
LL-DB

What Didn’t
Work

Issue Reference Root Cause Resolution Description Key Learnings Candidate for
LL-DB
PG193/PG196/ Delay in getting TC2 ATT has been having trouble Start the TC2’s in the
PG198 : Project approved through PRISM getting estimates approved in proper phase
Close out PRISM
PG195/PG198 Delay in closing out PRISM Apps needs to be more Ensure teams know what
gates responsive in closing out is expected from them
PRISM gates
PPA-IUP-WBTM-25 Proprietary Information Page 23 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.
 WPID F1.1-M Lessons Learned /
Retrospective

This project supports a July Point Release for delivery of functionality across a suite of applications used by the AT&T business field sales teams for
domestic and most of world (Impacts AT&T Corp). The goal of the Sales FMO (Future Method of Operation) Program is to effect a transformation
from our current method of sales operations to a world leading customer and selling experience that provides a significant competitive advantage
in the marketplace. The June release cannot support all of the required functionality so change requests have been identified to be moved to July.
The applications involved support Sales Opportunities, Design, Price, Propose, Contract, Order and Service Delivery. Functionality being added is to
support existing products and enhancements. The SOR experience for Sales should be consistent for all products, intuitive, minimize rekeying, and
flow pre-sales information to downstream ordering and provisioning systems. 121680a implements Sales FMO MACD functionality for Add BVOIP,
Replace and Reprice plus Remote Worker Enhancements and defect fixes.

08/30/2009

Target Deployment Start: 07/17/2009 Target Deployment End: 08/30/2009

PPA-IUP-WBTM-25 Proprietary Information Page 24 of 24

Not for use or disclosure outside AT&T family of companies except under written agreement.