Download presentation
Presentation is loading. Please wait.
Published byJulianna Hawkins Modified over 5 years ago
1
Group Work Breakdown Each member needs to have assigned an equal share of work Easily definable and measureable tasks Try to have the tasks independent of other group members as much as possible In your Phase 1 assignment, have a separate document that describes each members duties Each member should log their work to be turned in at end. You will each be asked to submit a peer evaluation and self reflection on the project.
2
Work Breakdown Structure
Often a project needs to be broken down into smaller tasks or activities These tasks together make up a work breakdown structure (W B S)
3
Work Breakdown Structure Properties
Each task or activity contains one deliverable, or tangible outcome, from the activity Each task can be assigned to a single individual or a single group Each task has a responsible person monitoring and controlling performance
4
Developing a Work Breakdown Structure (W B S)
Decomposition, starting with large ideas, then breaking them down into manageable activities Product oriented, building a website can be broken down into many parts Process-oriented, emphasizes the importance of each phase
5
A Sample Work Breakdown Structure
6
Time Estimation Techniques
Relying on experience Using analogies Using three-point estimation Identifying function points Using time estimation software
7
Beginning to Plan a Project by Breaking It into Three Major Activities
These may be different per project
8
Refining the Planning and Scheduling of Analysis Activities by Adding Detailed Tasks and Establishing the Time Required to Complete the Tasks
9
Using a Two-Dimensional Gantt Chart for Planning Activities That Can Be Accomplished in Parallel
Your activities will be different
10
Project Productivity Goals and Motivation
Successful projects require that reasonable productivity goals for tangible outputs and process activities be set. Goal-setting helps to motivate team members. You (students) seem to need “last minute” pressure to work on stuff
11
Ecommerce Project Management
Ecommerce and traditional software project management differences: The data used by ecommerce systems is scattered across the organization Ecommerce systems need a staff with a wide variety of skills Partnerships must be built externally and internally well ahead of implementation Security is of utmost importance
12
The Systems Proposal Cover letter Title page of project
Table of contents Executive summary Outline of systems study with appropriate documentation Detailed results of the systems study Systems alternatives Systems analysts recommendations Summary Appendices Ten main sections comprise the systems proposal. Cover letter—should list the people who did the study and summarize the objectives of the study. Concise and friendly. Title page of project—name of the project, the names of the team members, date submitted. Table of contents—useful to readers of long proposals; omit if less than 10 pages. Executive summary—precisely provides the who, what, when, where, why, and how of the proposal. Outline of systems study with appropriate documentation—provides information about all the methods used in the study and who or what was studied. Detailed results of the systems study—describes what was discovered about human and systems needs through all the methods described in the outline of the systems study. Systems alternatives—two or three alternatives that directly address the problem. Systems analysts recommendations—the recommended solution. Summary—brief statement that mirrors the content of the executive summary. Conclude the proposal on a positive note. Appendices—can include any information that may be of interest.
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.