Project manager IP 3

wilden

ip_2_software_project_manager_wilden.docx

Home >Computer Science homework help >Project manager IP 3

SWE440-1402A-01

Software Project Management

wilden

20 April 2014

Table of Contents 1 Project Description and Methodology 3-6 2 Project Plan Outline…………………………………………………………………………..7 3.ISO and IEEE Standards 8 4 Configuration Management 9 5 Defect Tracking and Reporting 10 6 Risk Management 11 7 Final Project Report 12 8 References 13

Project Description and Methodology

The IT ecosystem of financial services institutions faces many challenges in aligning business needs with IT solutions which generally span technology (delivery channels), regulatory compliance laws(Banking Laws BASEL III) and management. Because of large amount of regulation within the industry, banks and other institutions have continued to use the tried and tested approach of Waterfall model because of its perception of being predictable. But even waterfall model has its own cons. Customer satisfaction with the final applications may be lower even if the application fulfils all the features. The customer has be very patient with waiting for 2-3 years to see a finished product.

Financial institutions can address issues such as quality, time and cost by following agile methodology. A particular strength of this methodology is that it involves the customer in all areas of development leading to the creation of a more innovative and valuable information system.

We see that in this there is continuous review of what work has been done and continuous modification depending on the feedback of the client/user. So even if there is a change in requirement or change in any functionality, it can be modified effectively. It also improves the testing process as we first test small modules that we make and then by means of integration we move on to larger ones. This is the basis of agile model and this is what we are going to follow here.

Despite its advantage of working closely with the client and delivering satisfactory projects it faces a lot of challenge especially within large firms, which coordinate development between segregated team that work individually on one component such as design, analysis, development or testing. Shown below are challenges and stake holders in Agile Methodology.

Challenges in Agile Methodology

Agile Methodology Stakeholders

2. Project Plan Outline

Project management involves planning, monitoring and control of the people, process that occur in the process of evolution of software from a concept to a product. This generally focuses on People, Product, Process and Project.

We can view it on basis of 2 dimensions:

1. Project Life Cycle: Initiation, Planning, Execution, Monitoring, Control and Closing

2. Knowledge area: Scope, time, cost, quality, human resources, communication, risk procurement and integration.

Here our main focus area is project planning which involves estimation of effort, cost, resource and project duration, preparing project schedule and staffing, preparing risk management plan, project tracking plans and other plans such as quality assurance and configuration management plan.

Agile Project plan includes:

· Gathering all of the requirements.

· Performing analysis work on all of the required functionality

· Performing design work on all of the required functionality

· Developing code for all of the required functionality

· Testing all of the required functionality

· Deploying all of the required functionality.

· Take Customer Feedback.

We have also captured the set of tasks in Microsoft project manager that would be carried out once the project has been approved and given a green signal to carry forward. It only includes phases of developing code, testing the individual model and the integrated module, demo deployment, waiting for client feedback and if required rework.

1. ISO and IEEE Standards

Agile development

Agile software development is a way of organizing the development process by emphasizing on communication, frequent deliveries of working software modules in increments, short iterations of process, customer engagement throughout the whole development life-cycle of the project and change responsiveness. This can be seen as a contrast to waterfall-like processes which has detailed planning and design and consecutive plan conformance.

· The main constructs used in agile development are:

· Iteration: a short period of analysis, design, development and testing.

· Product backlog: a list of prioritized requirements for the product.

· Sprint: a selection of items from the product backlog being developed in an iteration.

· Sprint review: an evaluation of the outcome of a sprint, done with the customer to identify fulfilled requirements and the requirements needing further improvement. The term review here refers to review of the software being developed.

· Sprint planning: is done in the start of a sprint and results in a sprint backlog with items that in total can be developed within the timeframe of an iteration by the current team of developers.

· Stand up-meeting: a daily short meeting where each team member reports on progress, plans and problems.

ISO 9001 Standard

“This is a standard developed by International Organization for Standardization, that define, establish and maintain a quality assurance system for manufacturing and services industries.”

· The requirements of ISO 9001 are as follows:

· The company must have a quality assurance management process.

· The product’s quality is the responsibility of the management. As a result of this, the company’s management must make the necessary resources available for quality assurance work and training of employees.

· The company shall have one or more documented processes for product realization. The process must produce documents that can be reviewed for acceptance and used as proof of conformance at a later stage in case of any conflict or close up.

· All reports of non-conformances, both of the product or the process, shall be reported and analysed and should lead to a corrective action.

ISO9001 considers the document review process as its main verification and control mechanism.

IEEE Standard

IEEE standard for Information Technology-Software Lifecycle Process addresses issues relating to software life cycle right from the start of acquisition and supply, through development, to operations and maintenance. It provides a process framework upon which an organization should build its own framework for software lifecycle and it is tailor made to meet all project specific requirements.

As we are using agile methodology for developing the project assigned to us, we observe that there is a strict conformance between agile methodology and ISO and IEEE standards.

As for any kind of development methodology, an agile development project always starts by defining how the methodology shall be used in the given project. The process starts off by identifying the characteristics of the project environment. These may include the team size, organizational policy and project criticality. Next, the process requires that all the affected stakeholders of the project should be consulted. The planning of an agile project can easily be documented in a simple form specifying for instance iteration length, how to record and track requirements.

In between iterations, conformity to requirements is evaluated by the clients and records for the same of the results are kept as evidence of conformity. Here both the software product and related knowledge about it grows, the development team and the customer continuously improve their ability to discover potential sources of nonconformity. Code reviews are done in order to find bugs early in the stage and eliminate them as soon as possible. Such reviews produce improvement actions which demands immediate action and as a mean to proactively improve the development process for later development projects. Reviews are based on input from developers and customer feedback. Output from such retrospective are in the context of ISO 9001 be used as input to management review.

The main difference between ISO 9001, IEEE standard and agile methods is that ISO 9001 and IEEE insists on documentation for reviews and to demonstrate process conformity. Agile methods try to avoid writing documents that does not contribute to the finished system. On the other hand – if the customer requires a certain document, the use of agile methods are no hindrance for developing them.

One broad approach for ensuring that an agile development team conforms to the standard is to assign the task of providing that assurance to one or more individuals. In essence, then, this person enables the team to produce the necessary product in the manner required of the standard without failure.

Configuration Management

Defect Tracking and Reporting

Risk Management

Final Project Report

· Scheduling & Tracking Progress

· Dependencies between tasks

· Gantt charts with WBS and Milestones

· Program Evaluation Review Technique (PERT)

· Critical Path Method (CPM)

· Configuration management

· Risk management

References

IEEE12207. (n.d.). Retrieved from Wikipedia: http://en.wikipedia.org/wiki/IEEE_12207 ISO9000. (n.d.). Retrieved from wikepedia: http://en.wikipedia.org/wiki/IEEE_12207 Tor Stålhane, G. K. (n.d.). The application of ISO 9001 to agile software development. W.H. MORKEL THEUNISSEN, D. G. (n.d.). Standards and Agile Software Development.

Challenges Faced in Agile Methodology

Lack of Team Cohesion, Communication and Knowledge Sharing

Sub Optimal Governance

Sub Optimal support from organization and business users

Sub Optimal Team and Task Division

Agile Methodology Stakeholders

Business Analyst

Clients

Project Managers

Development Team and IT Operations

Project Management Office

Software Project Management Page 15