Industry guest speaker: Phil Hohn from I D Systems
Agile in System Management
will share the experience of implementing agile development systems processes in his company as the Process Improvement Project Manager.
Research is in applying agile to manufacturing systems. Using agile for the entire system development. When I look at this I look at project and quality management.
Waterfall/Spiral life cycles.
- MS Project - if you’re a project manager and you want an integrated schedule of where your project is.
Adjust the timing of the meetings from weekly to bi-weekly and even daily when you notice that projects are not progressing as forecasted initially.
Earned Value Management - something to look into.
Cost Performance and Scheduled Performance Indicators
- Your performance is based on these two indicators.
- Completing the task by your deadline you are getting a good CPI (vice versa for opposite)
- Break it down into manageable tasks that you can compete.
You should not start to design until you have all your requirements (after analyzing requirements and understanding if they are testable for quality).
AGILE:
You go with the riskiest one and design it. If they need some support to get going, you provide it.
Guide engaged communication with every member that’s involved with design.
SCOPE/CREEP
How you keep things within scope is by designing a system of traceability.
Waterfall Life Cycle Model
Linear approach with revisions of requirements throughout each stage.
Spiral Model
Take the riskier part of the design
Agile Model (advantages)
Incremental, iterative approach, open to changing requirements over time and encourages constant feedback from our end users.
Cross functional teams work on iterations of a product over a period of time, work is organized into a backlog that is prioritized based on business or customer value.
Encourages teamwork, accountability, and face-to-face communication. Business stakeholders and developers must work together.