Промышленный лизинг Промышленный лизинг  Методички 

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 [ 87 ] 88 89 90 91 92 93 94 95 96 97 98 99 100 101

iJJ..HI8

Chapter 4


Questions

When dealing with a waterfall methodology, can one proceed with the life cycle if the requirements have not been finalized and signed off on by all parties?

Define heavy and light methodologies.

Name the benefits of iterative development on a project.

Explain how you would convince your client or organization of the benefits of adopting a project methodology.

Does the type of organizational structure affect the efficiency by which projects are managed?

List five reasons that most projects fail today.

Based on your answers in the previous question, would a project methodology resolve these failures?

Describe the difference between the spiral and waterfall methodologies.

Answers

No, a waterfall methodology requires or emphasizes that one phase needs to be completed before the next phase begins. If the user requirements are incomplete, the subsequent phases become extremely complex, which is likely to result in schedule and cost overruns.



Heavy methodologies are predictive in nature, which results in many unsuccessful projects. A heavy methodology takes time; the design and deployment are dependent on each other. Light methodologies are more agile and adaptive in nature. They focus on being more informal, yet communicative. Light methodologies are designed and built face-to-face so that information flows more freely and swiftly than a heavy methodology would.

The benefits of iterative development on a project are: o

It encourages user feedback.

The system grows by adding new functions to each development iteration.

Misconceptions are identified upfront.

Continuous testing is performed throughout the project.

Allows for lessons learned on previous iterations.

The benefits of adopting a project methodology include: (1) it adds value to the business in terms of repeatable standard, (2) it provides a uniform way for projects to be managed, and (3) it provides a platform to introduce quality and planning into the project.

An organizational structure has a direct effect on the manner in which projects are staffed, equipped, and managed through the chosen life cycle. Large organizations with many departments working in a matrix or functional structure may take longer to complete than a project structure with everyone assigned by project rather than by department.

Most projects today fail because of: o

Poor communication.

Poor estimation.



Improper deployment.

Ineffective user requirements.

Poor change control.

Yes, a project methodology adds value to projects where no methodology is present. A methodology is not a silver bullet that excuses poor planning and deployment; instead, it guides the team on proper techniques and checklists, which will negate many of the obstacles found on projects today.

The waterfall methodology is the most common methodology found today. It is linear in approach most tasks are sequentially aligned to the previous and next tasks. The spiral methodology iterates the processes of planning, designing, building, testing, and delivering, until the system is ready to be released to the client.



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 [ 87 ] 88 89 90 91 92 93 94 95 96 97 98 99 100 101