Whether you are working for an organization, your own startup, or contracting business, software engineering requires that you consider which process to use in order to create a product. In this course, you encounter various models for managing software engineering processes that are successful in different circumstances. But, what happens if you choose the wrong process model for your project, do not follow any accepted process models, or do not follow the chosen process model correctly?
Think about these issues when responding to the following professional scenario that applies to your experience on the Professional Praxis.
After hearing from your supervisor that your Employee-Tracking Application team’s success has been noted by the organization’s senior leadership team, you see that you have an e-mail marked “urgent” in your inbox from Rowan Sawyer, senior leadership team lead.
Excited about receiving an e-mail from someone so high ranking in your organization, you quickly open it, read it, and respond to its request.
To prepare:
- Read the Rowan Sawyer E-mail document, located in this unit’s resources, and respond to its requests on the message board. The senior leadership team will monitor the message board for everyone’s response to their questions.
- To locate the potential process problems, compare the case study to the models in Chapter 9, Sections 9.3.4 and 9.5. Section 9.3.4 displays what the process should look like. Section 9.5 shows the product. Note: read the attached file Software project management: A process-driven approach.
Post on the problems that could arise in the case study’s process and explain how the problems could have been anticipated. Suggest two or three strategies you might use to prevent or correct the problems you identified.
