How to Proceed

1. Read through the case study provided and keep detailed notes on the key organizational issues involved in the case.
2. Make a Five Hundred words report to management providing recommendations on how to accomplish their goal of transforming the organization's waterfall lifecycle model to an agile approach. Your strategy for improving the organization's agility should include the following:
   1. A brief summary of the challenges that exist within the current waterfall model of the case.
   2. Application of agile principles and concepts required for the transformation.
   3. A redesign of the project team and brief explanation of the roles of each team member.
   4. Illustration of how the software development life cycle has to change.
   5. What tools you would recommend to help with requirements management.
   6. Due to the limits of what is provided in the case study, you will make recommendations on how to improve the organization's agility that rely on your own assumptions. Document the assumptions you have made that support your recommendations.
3. Submit your Assignment 1 Report through the dropbox in UM Learn.

The Case Study

A large-sized, security company that produces incident reporting software is seeing tough market conditions and stiff competition. While the cost for creating the software is steadily rising, its client's expectations are also rising because there are new, nimble players in the market who offer similar software at competitive prices.

Being in the health and safety industry, the security company operates within a regulated environment and, therefore, is routinely audited. Regulators have imposed a mandatory requirement to produce specifications and documentations in each phase without which the company cannot release products in the market. In addition, these documents go through a rigorous and version-controlled review process by departmental representatives. The documents are ink signed for approvals, printed and saved in a document repository. Signed hard copies are then printed and stored in locked cabinets under video surveillance. Any changes require the specification to go through another review process which adds further complexity, is extremely slow and cumbersome. The company's focus has been to comply to regulatory and citizen safety policies so that it may continue to operate in the market. As such, the user interface and software features are designed to prevent the company from entering lawsuits and to avoid regulators from revoking its license to operate. While the company is excelling in protecting its reputation and conforming to regulations, its customers are complaining that they are not receiving value for their investments. Version upgrades are too few and far in between. Due to heavy and sequential business processes and lengthy release cycles, a critical patch can take anywhere between 6 months to a year. Minor product enhancements take years to be released into the market. Due to delays, product enhancements often lose their value by the time they are released. For these reasons, the company is receiving flak in the market and is unable to attract new markets and retain existing ones. The company's bottom line profit margins are steadily declining. To survive and keep themselves afloat during this challenging time, the company has explored several avenues yet failed including rebranding and revamping their product. Currently, they have a multi-million dollar 5-year phased project in the pipeline that will add new features, workflows and design elements to the product.

The security company follows a traditional waterfall software development life cycle. In all, 25-35 documents are generated prior to project closure, depending on the size of the project. Reviews are performed formally through email and long bureaucratic processes. The organization uses a heavy weight content versioning system and requirements management tool that stores up to 50 pages long requirement specifications.

The project team comprises of co-located team members: a Project Manager, Product Manager, Developers, Quality Assurance Analyst and a Policy officer. Currently the software development life cycle looks like this:

Planning (6-12 months)

Analysis (3 months)

Development 12 months

Testing 3-6 months

Project Closure 2 months

Your goal is to improve the speed to market and increase the value delivered to the customer. You want to reduce the overall life cycle duration while improving value for this company's customers.