IS 556 Project Management

1
IS 556 Project Management

• Week 9 HOW TO HANDLE LARGE PROJECTS Divide and
  Conquer
• Readings On Time Within Budget - Ch.6

2
Large Software Projects

• Large Software Projects have extra challenges.
• Many tasks to coordinate and track
• Difficult to decompose task

3
Stepwise Refinement

• Not possible to figure out all task at once
• Use and iterative method to refine each iteration
• Increasing level of detail
• Not hierarchical components
• Not hierarchical calling relationship between
  higher and lower level modules
• Grouping items by logical order
• Coding modules exist at lowest level of detail

System
Continuously refine components
Comp 1
Comp 2
Comp 2
4
System decomposition and hierarical chart
Decomposition of high level into low level
components.
Hierarchical decomposition.
5
Functional Decomposition

• Decomposition into operational component as seen
  by user
• Part of requirements phase
• Objective is to define systems functional
  characteristics.
• Describe major functional operations of black box
  but nothing inside black box.
• E.g.,
• Might include
• ability to update account information from
  central computer to ATM
• Would not include
• communication method and/or protocol

6
Functional decomposition of large systems

• Sometimes functional decomposition is not clear
• A large inventory system might functionally
  include
• human interface, database, report generator,
  Update logic
• Might not functionally include human interface as
  high level
• Since above leaves out important functions such
  as fail-over backup
• Functional decomposition should create foundation
  for design decomposition
• A functional decomposition team may meet to
  define and select alternatives
• A good functional decomposition is selected based
  upon
• Reason (logical to divide a certain way)
• Ease of implementation (lead to a good design)
• Should mirror structured program (modules,
  independence, etc.)
• Comprehensiveness (everything covered)

7
Automatic Teller SystemFunctional Decomposition
Diagram
8
Design Decomposition

• Division into lower level components
• Lowest level coincide with software modules
• Usually done after functional decomposition
• Done in a stepwise fashion
• Best used as a method for providing increasing
  detail
• For example, might decide main functional
  components of ATM system are
• The automatic teller terminal
• The main computer
• The computer network

9
Design Decomposition

• Good design is basis for software structure
• Software Engineering has lots to say about design
  decomposition
• Independent software components
• Simple interfaces (minimize coupling)
• Information hiding
• Produce modules that hide their design and data
  structures (enable simple changes to data
  structure)

10
Automatic Teller SystemDesign Decomposition
Diagram
This level might be actual software modules
11
Work Breakdown Structure

• A method of decomposing tasks for project plan
  using stepwise refinement
• Derived from statement of work
• Used to track status and assignment data
• ALL work must be part of a task in this document
• Over time the WBS is refined (tasks added)
• Use WBS to assign resources to tasks
• Many different tools exist to create project
  plans (e.g., Microsoft Project) from WBS

12
Work Tasks

• WBS Represents all work tasks (not software
  components)
• Each low level design decomposition module has 3
  tasks
• Design
• Coding
• Unit testing
• Would also include non-development tasks
• Acquire development machines
• Install test machines
• Set up change control system
• Training
• Staffing

13
Work Breakdown Structure Task Designation
14
Large Projects and Subsystems

• Subsystem contains most characteristics of main
  system
• Massive projects require division into subsystems
  (each make be looked at as separate systems)
• Coordination across subsystems is the key

15
Component Based Development

• Components advantages
• Known commodity
• Refined over time
• Reuse saves time and money
• Effective on large projects
• Equivalent to parts on a shelf
• Example Microsoft Windows plug and play
• Application interfaces

16
Situational Leadership Model

• Decision Styles
• Leader-Made Decision
• Leader-Made Decision with Dialogue and/or
  Explanation
• Leader Follower-Made Decision or Follower-Made
  Decision with Encouragement from Leader
• Follower-Made Decision

• Task Behavior
• Goal Setting
• Organizing
• Directing
• Controlling
• Relationship Behavior
• Giving Support
• Communicating
• Active Listening
• Feedback

17
Communication Channels
Upward Communication to Management
Lateral Communication to Friends, Social Groups
and both Formal and Informal Organizations
Lateral Communication to Peers, Other Functional
Groups and Customers
Project Manager
Downward Communication to Subordinates and
Project Office Personnel
18
Class Expectation Topics

• Budgeting
• Resource Mgmt
• Deadlines
• Milestones
• Requirements
• Risks
• Dependencies
• Justification
• Creating a collaborative environment (team
  building)
• Documentation Strategy

• Communication strategy
• Change management
• Expectations
• Multiple Projects
• Task Scheduling
• Key Players
• Executive Sponsorship
• PMI Certifications
• Methodology for PM
• Critical Path
• Scope
• Software tools for PM