Choose the Project Methodology: A key decision is the methodology that will be used for your project. A traditional waterfall methodology is highly structured to deliver good results, but can result in longer projects based on its sequential set of tasks. Agile methodologies deliver quicker results, but require managing cross-functional teams and allowing them more freedom to create prototypes in several iterations as requirements are refined.
Identify Requirements: A solid understanding of user requirements forms the foundation for your software, yet there's often a rush to skip this and move to the coding phase. This may cause you to miss necessary requirements or try to meet an ever-changing target as new requirements are uncovered.
Understand the Technology: It's crucial that the project manager understands the maturity level of the technology used for the project, since technology changes at a rapid pace. If it's a well-understood technology, the chance of meeting the project schedule is high.
Communicate with Business Stakeholders: Technical jargon is a foreign language to most business stakeholders, so communication between the project manager, the technical team and other stakeholders can be a challenge. Project managers and technical team members need to talk about the requirements and project risks using business terminology. If users can't understand the explanation, they can't make informed decisions about the level of risk they're willing to accept.
Deliver Phased Results: Many software projects are large, expensive and lengthy efforts. Often the new software isn't delivered until months or years after the requirements were originally documented.
Understand the Culture: Project managers should consider cultural issues in the project planning. This includes adding contingency time in the schedule to work through possible issues and clearly communicating the risks of taking short cuts.
To Download: http://www.megaupload.com/?d=V7SOKFOZ
No comments:
Post a Comment