learn your project vocabulary
TRANSCRIPT
* 1. Data Dictionary definition
* 2. WBS definition* 3. Data Mapping definition* 4. Progressive Elaboration
definition* 5. Configuration definition* 6. Milestone definition* 7. Customization definition* 8. SME definition* 9. PMP definition* 10. Workflow definition
* 11. Reference Table definition* 12. SIT definition* 13. UAT definition* 14. Lessons Learned definition* 15. Project Artifacts definition* 16. Project Repository definition* 17. User Stories definition* 18. Regression Testing
definition* 19. Change Order definition* 20. Marketing and
Communication Plan definition* 21. Data Crosswalk definition
Vocabulary
1 . Data Dictionary•a set of information
describing the contents, format, and structure of a database and the relationship between its elements, used to control access to and manipulation of the database.
2. WBS•A work breakdown structure
(WBS), in project management is a deliverable-oriented decomposition of a project into smaller components. A WBS is a key project deliverable that organizes the team's work into manageable sections.
3. Data Mapping• In computing and data management,
data mapping is the process of creating data element mappings between two distinct data models. Data mapping is used as a first step for a wide variety of data integration tasks including: Data transformation or data mediation between a data source and a destination.
4. Progressive Elaboration
•Progressive elaboration is a continuous iterative process of refining and further detailing the product characteristics based on more detailed information and insight that becomes available as the project progresses.
5. Configuration•A process where an off the shelf
software program is tailored with data or settings that are needed for the District to use the software effectively. These changes are not affected by an upgrade to the software. Other than time configuring, no cost is associated.
6. Milestone•An important event or
completion goal in a project where an objective is achieved. Knowing upcoming milestones helps keep the project team on track.
7. Customization•A software development
process where off the shelf software is customized in the way it operates to meet District needs. These changes require a Change Request and will have additional costs associated with it.
8. Subject Matter Expert•Someone that is
knowledgeable in a specific job role or discipline and assists the Project Manager in defining tasks to be tracked in a project.
9. PMP•Project Management
Professional (PMP) is a global certification that is achieved by matching years of documented experience and training, and is achieved by the successful completion of a four (4) hour examination.
10. Workflow•the sequence of administrative,
or other processes through which a piece of work passes from initiation to completion. Process includes the creation of on-line forms as well as defining the path the form is to follow.
11. Reference Table•In the context of database
design a reference table is a table into which a pre-designated set of possible values of a certain field data type is entered.
12. System and Integration Testing
•A process where the hardware, interfaces, and software installation are tested by the installer to ensure that the software is prepared to be released to the District.
13. UAT•User Acceptance Testing
(UAT) is an effort by the project team members to test the functionality of the software in preparation for Go-Live.
14. Lessons Learned•A session where the team
members gather to document in some detail the acquired knowledge from the project effort.
15. Project Artifacts•Documents that are created
in the Project Initiation Phase that detail the project goals, constraints, participants, expected costs and success factors.
16. Project Repository•A centralized shared location
where the team can access files that are specific to the project. Our repository is O:\SUNGUARD.
17. User Stories• User stories are short, simple descriptions of a feature
told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template:
• As a <type of user>, I want <some goal> so that <some reason> meets my <condition of satisfaction>.
• User stories are often written on index cards or sticky notes, stored in a shoe box, and arranged on walls or tables to facilitate planning and discussion. As such, they strongly shift the focus from writing about features to discussing them. In fact, these discussions are more important than whatever text is written.
• Great step in developing a test plan
18. Regression Testing•A second or third pass
through the test plan for issues that have been identified and reported as fixed by either SunGuard or other team members.
19. Change Order•A process where new
customizations for the software are documented and submitted to SunGuard for estimation of timeline and cost for development.
20. Marketing and Communication Plan
•A plan that documents the process, method, message, and schedule to facilitate transfer of knowledge of project team to all District audiences.