Chapter8-WorkflowsOfTheProcess

Chapter8-WorkflowsOfTheProcess - Chapter 8 Workflows of the...

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

View Full Document Right Arrow Icon

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

View Full DocumentRight Arrow Icon

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

View Full DocumentRight Arrow Icon

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

View Full DocumentRight Arrow Icon

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

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

Unformatted text preview: Chapter 8 Workflows of the Process Taken from Walker Royces textbook Software Project Management plus a number of Personal Comments Overview Introductory Remarks 8.1 Software Process Workflows 8.2 Iteration Workflows Introductory Remarks We like sequential activities. Human nature. KISS technique. We basically perform activities sequentially But Teams must operate in parallel. Requires synchronization, cross-checking, Managing these workflows is a primary source of management complexity and leadership. Times have changed from the old days. We are required to more in less time with more tools, better support environments, but with very high expectations! Old Way for Tracking Workflow: Sequential Activities In the past, projects progressed via sequential progress through fixed activities. Successful projects had boundaries not rigid; non-adversarial stakeholders Unsuccessful projects had rigid boundaries. All activities had to be completed before pressing on Much work spent on details (such as completing a manual) while slighting important development / engineering activities. Requirements subtasks subtasks . Design Preliminary Design Detailed design (mgmt level) different granularities Coding Testing document prep. Implementation Travel/ install Jan Feb Mar Apr May June July Aug Sep Oct Nov Dec Jan . Gantt Chart Civilian Pay System : System Code: BQ New Way for Tracking Workflow: State of the Project We now avoid naming life-cycle phases after the predominant activities . Now we track the state of development within phases (inception, elaboration, construction, transition), recognizing that activities and artifacts evolve and eventually become stable. We develop incrementally producing executables along way. Avoiding a discrete set of lock-step activities and cut- off / due dates. The state of a project can be tracked via the minor milestones (end of each iteration). This is a VERY HARD SALE to management!!! 8.1 Software Process Workflows We have spoken about fundamental sets of artifacts and the phases in which they are largely produced recognizing the evolution of these artifacts. (Scan Chapter 6) We now need to look inside the phases and the iterations micro-level. Interestingly , within these boundaries, we will use the term workflow , and talk about a thread of cohesive activities that are mostly sequential. The Workflows will be mapped to the product artifacts and to the teams So, lets look at high-level workflows. Workflows vs Core Process Disciplines and Core Supporting Disciplines Recognize that your text is a wee bit dated. Process Workflows (formerly eight) are now referred to as Core Process Disciplines and Core Supporting Disciplines....
View Full Document

This document was uploaded on 07/29/2011.

Page1 / 24

Chapter8-WorkflowsOfTheProcess - Chapter 8 Workflows of the...

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

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