ERP-HR&Communication-rev2

ERP-HR&Communication-rev2 - ERP Project Team and...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
1 July 10, 2007 1 ERP Methodology and Project Management ERP Project Team and Project Communications Ronald E. Giachetti, Ph.D. Associate Professor Industrial and Systems Engineering Florida International University July 10, 2007 Slide 2 Agenda s Theory underlying team structure s ERP project team examples s Staffing ERP projects s Project communications Communications planning Reporting Communication with users s Summary
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 July 10, 2007 Slide 3 s Communication is the main mechanism to coordinate activities in a project s Coordination is needed when there is a dependency between two or more activities s Two main issues: Proper project organization establishes communication structure Appropriate communication medium for the message July 10, 2007 Slide 4 Amount of Communications s Too much communication is as bad as too little s Too Little : Results in an ERP project that does not come together s Too Much : Results in too much time coordinating efforts and not enough time developing the ERP system
Background image of page 2
3 July 10, 2007 Slide 5 The Right Amount of Communication s In the Mythical Man-Month , Fred Brooks points out that individual productivity decreases as the number of developers on a project increases s Two types of work Actual Work – defined as the work that adds value to the project Coordination Work – defined as the work that a group performs that an individual performing the same task would not perform July 10, 2007 Slide 6 s Different structures lead to different level of communication s ERP problems are too big for an individual to handle: the whole idea is to use the entire organization as a distributed processing unit s Capitalism versus communism decentralized decentralized Most satisfaction decentralized centralized Least errors decentralized centralized Least time centralized centralized Fewest messages Complex Task Simple Task Variable
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 July 10, 2007 Slide 7 IT Project Structures s Functional s Unstructured s Product Team July 10, 2007 Slide 8 Functional Structure Customer System Engineer Software Architect Developer Team Test Team Customer Software Requirements Requirements Software Design Spec. Integrat ed System Delivere d Program Manager • Too little communication • Difficult to integrate subtasks and parts into the whole ERP system • No shared responsibility – everybody did their job well but the system is disappointing
Background image of page 4
5 July 10, 2007 Slide 9 Unstructured Team Customer Architect Developer Developer Developer Tester Program Manager • No defined team structure •Too much communication (much of it ineffective) • It can occur when a team grows from 3 or 4
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 28

ERP-HR&Communication-rev2 - ERP Project Team and...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online