We don't do things right the first time

We don't do things right the first time
1. Lack of Knowledge
2. Unclear Priorities / Objectives & Mandate
3. Lack of resource (time, Budget, availability)
  1. Available pool of skilled labor is limited
  2. Difficult to substantiate request for budget
  3. Many activities
4. Lack of Harmonization between departments
5. Resistance to formal Processes
6. Incomplete Upfront Project/Domain Vision Definition
Requirement Management
1. Lack of resource (time, Budget, availability)
  1. Available pool of skilled labor is limited
    1. Many other OEMs working on new programs
    2. Lack of coaching or mentoring
  2. Difficult to substantiate request for budget
    1. Lack of knowledge to quantify business needs ($$)
    2. Lack of time to do the background work
      1. poor planning
    3. Lack of experience
      1. Projects are unique
      2. Introducing new things
      3. Project documentation & schedules are not kept so that it can be reused
  3. Many activities
    1. Poor Planning
      1. Accept everything
      2. Don't know how to plan
      3. Constantly Underestimating level of effort
    2. Many unplanned activities
      1. Processes are not followed
      2. Bad processes
      3. Lack of subject matter knowledge
      4. A lot of adhoc activities
      5. Activities have not been formalized
2. Previous
  1. Lack of Knowledge Management
    1. Can't find what was done on previous programs
      1. Don't leverage existing knowledge & BA. People keep re-inventing the wheel
      2. lack of Simulation & test data management on CSeries
      3. Lost data & insufficient data reuse from program to program
      4. Jumping to solutions without proper analysis (ex AE, assigning objectives to push AES)
  2. Management Issues
    1. Management does not always make decisions at proper time
      1. Sometimes upper management isn't aware of decisions made at lower levels
      2. Bad financing. No core budgets
      3. lack of support from top for AES
      4. Not enough long term strategic planning
  3. Lack of Harmonization between departments
    1. Lack of harmonization of expectations between departments on same program
      1. lack of harmonization between departments in general
      2. Insufficient business planning/collaboration between technical & stress groups
      3. lack of collaboration (open to accept feedback)
      4. BA's internal objectives overshadowed by ITs objectives
  4. Weak Planning
    1. Activities on program are not properly planned
      1. BA program schedule does not include all RM activities
      2. Lack of planning for IT budgets & support
  5. Poor Quality of Deliverable
    1. Multiple revision of documents
      1. Writing first time quality requirements
      2. Writing vague requirements
      3. Low RM deliverable quality
      4. ARP4754 RM plan insufficient for ARP4754 (incomplete, low quality)
      5. Configuration Management / Change management plan on CSeries delivered late and not approved. Not deployed. Unachievable plan
  6. Resistance to formal Processes
    1. Not all departments have defined processes documented
      1. People do not follow defined processes
      2. Designing workarounds to processes
      3. How BA implements ARP process
      4. People who start new programs are not always aware of what needs to be done
      5. Insufficient/nonstandardized methods development
  7. Lack of Systems Engineering approach
    1. Weak system decomposition
      1. Data & process auditing weak
      2. Data & process alignment weak across BA
      3. No use cases
      4. Lack of System modeling
      5. No validation up front for requirements
      6. Forgot break pedal on the CSeries
  8. Lack of Team spirit
    1. Little or no team building activities
      1. People are reluctant to go against the current due to company politics. Scared to stand up for change
  9. PMPs & PDPs happening late in the year
  10. Poor Project Management Execution
    1. Missed milestones schedule
      1. Missed dates on project plans
  11. Lack of expertise
    1. The supplier does everything. BA does not need as much expertise
PDM
1. Symptoms
  1. Need to re-scope/descope the project
  2. Need to stop the project development and return to the design board
  3. Need to stop the project development and return to the BU requirements
  4. Working in the wrong direction
  5. acting before planning / planning before checking or grasping situation
  6. Recreating material instead of reuse (eRoom)
  7. Difficult to find and access information (eRoom)
  8. Difficult to find and access latest information (eRoom)
  9. BM takes weeks to written because information not available
  10. training material need to be reworked because the material is not ready on time or has a poor quality
  11. repeat meetings because of key members lack of time/participation
  12. Solution doesn't meet business requirements
  13. Incomplete document
  14. Business not informed of the as-is processes
  15. Requirements in the IT document not clear for the business
  16. Business do not recognize their needs in document
  17. Business do not understand document
  18. Business not happy of the delivery dates and delays
  19. Business not happy with the solution
  20. Project exceed budget
  21. Business not happy to see only Power Point presentation of the solution
  22. Business complaint about lack of planning & communication
  23. Business complaint about scope creep
2. Scope not clearely defined
  1. Scope not well identified
  2. Unclear Project Scope
  3. Scope changes during the project
3. Lack of resource (time, expertise, headcount)
  1. Lack of PLMP and business participation
  2. Scope and delivery dates not realistic with budget and resource
  3. Lack of time & budget for training
  4. Lack of planning (maily for mid & long term plannning)
  5. Lack of time & budget from key resources
  6. Lack of expertise
4. Divergent Priorities
  1. Business informed at the last minute for participation
  2. Unclear R&R
  3. Lack of clear communication
  4. Lack of business involvement to define process & requirements
  5. IT priority is to deliver solution
  6. Requirement & Process documentation is a low priority for the business
  7. IT not capable to use business terminology in their document
  8. Lack of synnergy between IT & PLMP
PPD & CAE
1. No standard process framework
  1. Poorly defined deliverables
    1. no clear R&Rs
  2. Little or no standard work
2. Incomplete Upfront Project/Domain Vision Definition
  1. time constraints
    1. too many projects
      1. too many programs
      2. lack of portfolio prioritisation
      3. unclear prioritisation methodology
      4. unclear value management processes
  2. lack PLM process skills and experience
    1. availability of resources on market
    2. project leader is incapable of synthesizing a vision
      1. lack of formal training / coaching
      2. wrong personality type
    3. junior resources fulfilling senior roles
      1. availability of resources on market
  3. immature PLM solution capabilities
    1. technology readiness level for aerospace
    2. continuously evolving business environment
  4. unclear mandate/scope
    1. time constraints
      1. too many projects
      2. insufficient resources
    2. too many projects
      1. lack of portfolio prioritisation
      2. unclear prioritisation methodology
      3. unclear value management processes
      4. too many programs
    3. inconsistent breakdown of domains
    4. problem complexity
      1. poor roles & responsibilities
    5. alignment across BA teams (IT, PLMP, PLM CC, APD, et al
      1. poor communication
3. nature of responsibilities
  1. responsibility is abstract with unclear deliverables
    1. unclear mandate/scope
  2. activity may require iterative process rather than arriving at best solution immediately
  3. low empowerment levels to accomplish activities
4. Unclear PLMP Mandate
  1. different levels of management perceive mandate differently
    1. top-down communication
5. Poor project workflow
  1. no clear phase/gating system
  2. lack of resource involvement by PMs
  3. time constraints
    1. schedule, resource, budgetary considerations
  4. lack of portfolio management
    1. budget and resources
6. Lack of collaboration from other BA teams
  1. Other team's understanding of PLMP's R&R
    1. poor internal understanding of mandate
Collaboration & CS
1. We do not know what needs to be done
  1. Unclear Priorities / Objectives
    1. There is conflicting priorities/objectives
      1. Multi-Program Support, Short vs Long term goals, budget allocation (we work only if we have money to spend on that program)
  2. Unclear R&Rs
    1. New organization which has not clearly defined our value added within the IT/BU environment. Our role as the owner of product development processes is not recognized nor understood.
      1. Since our organization is in Engineering, the perception is that we only serve Engineering processes not the full PLM processes from conception to in-service.
      2. We have not properly defined the value we bring to IT projects and to the various BUs
      3. PLM does not know what being owner of the product development processes means
  3. Lack of Knowledge
    1. 1. Why do we a lack of Knowledge
      1. We do not exploit the experience of employees hired
      2. 2. Why do we not exploit the experience of employees?
      3. Steep Learning Curve of new Employees due to Project Time Constraints
      4. 3. Why do we have a steep learning curve?
      5. Employees not having experience with BA processes
      6. Employees not having BA Culture Experience
      7. Multitude of subject matters makes it difficult to have full knowledge of every process
2. Symptoms
  1. Kenexa survey inputs
  2. Errors in execution of our deliverables/processes – more effort is required to do the work
  3. Work needs to be redone/repeated
  4. Many teams working on the same deliverables
  5. Individual workload surpasses expectations
  6. Committed delivery dates are rarely met. Planned vs execution.
3. Objectives
  1. Clarified Roles & Responsibilities between PLM teams, IT and BUs
  2. Team focused on Priorities and setting priorities according to our strategic direction
  3. (right size our involvement)
  4. Clear and agreed upon delivery dates with an understanding of the impacts of not delivering
  5. Quality deliverables
4. Measure
  1. Results from next year’s, Kenexa survey
  2. Survey given to PLM, IT & BUs on R&Rs
  3. Track start & end dates of deliverables
  4. Survey on the quality of the PLM deliverables sent to IT, BUs & Management
MFG
1. Unclear Priorities/ Objectives & Mandate
  1. Symptoms
    1. Frustration & Stress Levels AES Standups
    2. Schedule / Quality / Scope / Cost Impact & Changes
    3. Project Expectations not realized
    4. Decrease risk/issue Visibility at IPDT's
  2. Objectives
    1. Stress Free Objectives & Scope Realization throughtout project activities
    2. Common BU Strategy and Resource Forecast
    3. Increased Departmental influence & budgeted FTE's
  3. Measure
    1. Levels of Communication between PLMP SU's and IT
    2. AES STandup Stress Levels
    3. Limited Budget Variance
    4. Progressive Return on Investment