MANAGEMENT
ARTIFACTS
BY
NAAILA -1252
SADIA -1220
MANAGEMENT ARTIFACTS
●
●
In software project management, management artifacts are documents or
tangible items that provide information about the project's planning, progress,
and outcomes.
These artifacts play a crucial role in facilitating communication, decisionmaking, and overall project governance.
Divided into 2 categories:
1. Planning Artifacts: Documents or items created in the early stages of a project
to outline strategies and structures for achieving objectives.
2. Operational Artifacts: Documents or items guiding day-to-day activities and
ongoing management during project execution and maintenance.
PLANNING ARTIFACTS
1. Work breakdown structure
2. Business Case
3. Release specifications
4. Software Development Plan
1. WORK BREAKDOWN STRUCTURE (WBS):
Description:
● Hierarchical decomposition of project tasks.
● Breaks down the project scope into manageable work packages.
Example:
● Phases: Requirements gathering, design, development, testing, deployment.
● Tasks: Creating wireframes, coding modules, user acceptance testing.
2. BUSINESS CASE:
Description:
● Justification for the project.
● Outlines objectives, benefits, costs, and risks.
● It helps stakeholders understand why the project is necessary and what it aims to achieve.
Example:
● Highlights market demand, revenue projections, development costs.
● Emphasizes competitive advantage for the organization.
3. Release Specifications:
Description:
● Details features and enhancements for a software release.
● Aligns development with business goals and user expectations.
Example:
● Version 1.0 features: User authentication, data input forms, basic reporting.
● Outlines what users can expect in the initial release.
4. Software Development Plan:
Description:
● Comprehensive document outlining project execution.
● Includes scope, schedule, resources, quality assurance, risk management.
Example:
● Specifies agile methodology, two-week sprints.
● Defines roles, responsibilities, tools, technologies, testing, deployment.
OPERATIONAL ARTIFACTS:
Operational artifacts in project management are essential documents and
items that guide day-to-day activities and ongoing management during project
execution and maintenance.
1. Release Descriptions
2. Status Assessments
3. Environment
4. Deployment
5. Software Change Order Database
OPERATIONAL ARTIFACTS
1. Release Descriptions
Purpose: Describe the results of each software release, including performance against evaluation criteria.
Importance: Includes performance details, evaluation criteria from release specifications,
and substantiation through demonstration, testing, inspection, or analysis.
2. Status Assessments
Purpose: Provide periodic snapshots of project health and status.
Importance: Covers risk assessments, quality and management indicators, resource review, staffing,
financial data, top 10 risks, technical progress, major milestone plans and results and scope.
3. Environment
Purpose: Defines the development and maintenance environment as a first-class artifact of the process.
Importance: Includes requirements management, visual modelling, document automation, programming tools,
automated regression testing, continuous and integrated change management, and feature/defect tracking.
4. Deployment
Purpose: Transition the product into operational status.
Importance: Varies based on the project and may include subsets for system delivery to a maintenance
organization, computer system operations manuals, software installation manuals, cutover plans, site surveys,
marketing plans, sales rollout kits, and training courses.
5. Software Change Order Database
Purpose: Manage change efficiently in an iterative development process.
Importance: Greater change freedom allows for more productive iterations. Automation is key to achieving
flexibility and managing change efficiently.
THANK
YOU