I'm in process of making a generic Project Methodology for software development including following points: 1. Resources in Project Team, viz. Technical Account Manager, Project Manager, Lead Designer/Architect, Lead developer, Lead QA Engineer, and other developers/admin 2. Project Initialization steps 3. Development Overview 4. Development Process 5. Continuing Process development 6. Requirements Document 7. Software Design 8. Approve Project Plan 9. Change Request Form 10. Impact Assessment and Approval Plan 11. Generic Project Status Report 12. Generic Bug list 13. Complete Deliverable form 14 Evaluation form
ETC
I would appreciate if anyone know about the above points or if someone has a similar document.
Thanks a tons Saving Changes...
Sort By:
Stephen MayeSenior Vice PresidentVa, United States
You can probably find examples of several of these on this site. Other gantthead users may have some favorites they can point you to or provide. I don't know if you've searched yet, but even within the unpaid content on the site, there are a lot of good assets.
We have two methodologies, development and project management. Both methodologies are separate, but related. Having either one of them wrong can cause project hardship.
What we did at my company is an integration of development methodology and project management methodology. We have a great development methodology that has evolved over the last 10 years. For project management we use the PMBOK as our base.
We then identified integration points. We defined the development methodology into initiation, definition, development and deployment. These overlap with the PM phases initiation, planning, execution/control, close – out. As well I defined a template WBS for our development methodology. Get them hooked on PM methods early!
The biggest advantage we find is that are we know that if the PM phase is not aligned with the development phase then that’s a risk. If we are not out of definition in the development phase in development, then we really should not be out of planning in the PM methodology. If we are in executing and controlling and we need to revisit definition that’s a change order.
In my mind the key to defining a good generic PM methodology for software development is having one or two people who understands both your methodologies and then determining the integration points that fit your company.
The integration (versus a merger) gives flexibility to both methodologies. We have best practices for each that not only includes the process, but the timing.
I have rambled enough for now. Email me off line if you want more detail. Saving Changes...
Patrick Roosemgr| Care Automation bvbaLinde, Belgium
Hi, At my customers we have implemented a framework for PM software development lifecycle based on "best of all worlds": - Component Based Development - Catalysis - Rational Unified Process - Waterfall !!! yes because 90 % still is dedicated to non-iterative development cycle - Xtreme Programming Then we mapped the framework onto a case-tool to be 100% independant of the tool supplier. For each phase and each step in the framework deliverables as templates and action and role descriptions were developped.
The deployment process (for a very large cy of +1600 ICT consultants): - drawing an agenda for uniformization the writing notation ... UML - providing training / mentoring / coaching the teams
The framework has been tested, approved and is in deployment phase. contact: [email protected] Saving Changes...
Anonymous
Hello I am a consultant for many years at DMR and our company has developed a complete Project Management and System Development methodologies since 20 years. It is a web based environment and it also included documentation, templates, navigation and more. You may want to take a look at www.dmr.com Saving Changes...
To make a generic SW development project methodology means to prepare standards, naturally between many other things. "New" or tailored methodology - it makes no matter.
Tarun: Please refer to SW-CMM of the SEI (Software Engineering Institute), that includes some guidelines for software development process (focus only in the Level 2 of CMM that implies some process areas that adress most of the project management issues). Anyway if you need more help I've worked a lot on developing models based on PMI/CMM, don't hesitate to email [email protected].... Take care
