Professional Documents
Culture Documents
Untitled
Untitled
Untitled
0
Project Offshore - Centre Management Workstream
Mid Year Catch Up
Monday 10/06
16:00 Arrive from airport; meet the team and introduce Ian Betts
Tuesday 11/06
09:00 Catch up meeting with the whole team: Update PQS 2.0 plans, outstanding work, ODS change process, system documentation and Quality Assurance walkthrough 12:00 Lunch 14:00 Team A: Sprint 6 LPM planning & sizing session 16:00 1.5 migration brainstorming session (Vlad, Mihai, Ion)
Wednesday - 12/06
Team Gari: Sprint 1 - Learner CRUD planning & sizing session Lunch Documentation workshop (the whole team) Free time
Thursday - 13/06
PQS 2.0
04/06/2013
Sprint 6 from 10/06 to 21/06 Extra Sprint 7 from 24/06 to 05/07 Finish development & release to UAT on 08 July
Sprint 1 resuming on Monday 10/06 to 21/06 Sprint 2 from 24/06 to 05/07 Scope is reduced to Learner CRUD only Finish development & release to UAT on 08 July
Migrate 1.5 applications into PQS 2.0 Allocations; Access Arrangements; Post Result (Special Considerations); Non ePen Assessment; FS/ICT & BTEC/NG - Data Merging? ODS refactoring?
PQS 2.0
04/06/2013
PQS 2.0
04/06/2013
PQS 2.0
04/06/2013
http://ukedxepsweb01.peroot.com/sites/PQS%202.0/PQS.Base/ODS/Forms/AllItems.aspx https://drive.google.com/a/pearson.com/#folders/0B6SgkUl5o0EhS0h1bE1NY0ZyMHc
Database renaming ODS schemas for Centre Management
Persons - common Addresses - Common TelephoneNumbers - Common EmailAddresses Common Organisations - customer OrganisationGroups - customer OrganisationGroupMembers - customer OrganisationIdentities - customer OrganisationContacts - customer OrganisationAddresses - customer OrganisationAddressTelephoneNumbers - customer OrganisationEmailAddresses - customer OrganisationAchievables - customer LookupOrganisationAchievableStatuses - customer LookupOrganisationAccessLevels - customer LookupOrganisationFundings - customer LookupAddressTypes - customer LookupCentreTypes - customer OrganisationChangeRequests - customer OrganisationPropertyChanges - customer
PQS 2.0
04/06/2013
Description This schema contains all data associated with the awarding process. (Example GradeBoundaryAwarder,AvailableAssessmentGradeBoundaryAllocation etc)
Integration Schema's
Description This schema contains tables that hold data related to systems we integrate with. The design is abstract so allow quick replacement of systems we do not have control over and who's future is uncertain (Example ExternalSystem and ExternalSystemParameter). Some of our key entities my be associated with tables in this schema but the dependancy should be one way. That is SystemIntegration data may rely on key Business Entity/Proccess data but this should never be the other way arround.
Description This schema contains data used to fullfill the grade boundary functionality supplied by Novus.
PQS 2.0
04/06/2013
PQS 2.0
04/06/2013
10 PQS 2.0
04/06/2013
11 PQS 2.0
04/06/2013
Starting from the 8th of July, both teams will be working on this activity;
12 PQS 2.0
04/06/2013
Just Enough The bear minimum which is needed to explain what the system does and how it works;
Screen shots with brief description; Flow diagrams showing processes and logic flow; Domain Models to pinpoint the entities and relationships;
13 PQS 2.0
04/06/2013
14 PQS 2.0
04/06/2013
15 PQS 2.0
04/06/2013
Allocated Traditional Marking display the list of Traditional Marking orders already allocated. This screen gives the possibility to Reallocate AA and Send notifications. Hovering an item in the grid will show a tool-tip.
16 PQS 2.0
04/06/2013
Helps the developer to ask questions, allowing to spot and anticipate issues;
Aids System Test allows tester to understand workflow, identify status changes and table updates, create accurate expected results; Documentation should be created during the whole process, since the very beginning of the story discussion, till the end of the testing, and mainly by the developer himself;
17 PQS 2.0
04/06/2013
18 PQS 2.0
04/06/2013
Quality Gates describe the criteria (Who, What, When, How, Where) to be met before we can move from one phase to another. They are simple control points reminders of what we should have done and what needs to be in place to move forward. Example: QG2 QG1 passed DoD passed Code review passed What to test agreed Processes confirmed Test data created / available System Test environment on-line and stable
22 Presentation Title runs here l 00/00/00
PQS 2.0
Thank you!