Programme & Project Management

Company is moving down the path of strict Solution Development Life Cycle (Project Life Cycle) and need a good user friendly software that will aid a fortune 200 group with basic SDLC process management. Lots of products on the market that claim simply and easy to adopt but looking for more real-life experiences for a good application to manage the process. Ideally the application would be integrated with the MS Project 2003

I’d suggest building your own, or using Team Foundation Server. Anything else is going to make you the rat in the maze instead of giving you control of your software. Implement a good source control paradigm. No software is going to do that for you. It’s more about good habits than good software.

NADC-82183-50
subprograms that can be freely shared. The programming language used
greatly affects the generality of software modules. But the software
engineering environment also affects the ability to know about the
software components as well as the freedom to access them. SEE will
provide convenient support of software sharing.
Reproducibility
The Navy must be able to reproduce its software. This means that
the Navy must have control over the tools used to generate the
software. A contractor’s proprietary tools must not be part of the
software development process because they tend to lock the contractor
into the project for the entire life cycle. Also, the Navy must limit
users’ ability to make arbitrary changes to their data base informa-
tion. For example, if someone can modify the object code so that it
does not reflect the associated source code (a current capability of
the MTASS SYSGEN) then the Navy cannot always reproduce the object
code from the source.
Standardization
Standardization is essential to the above topics. It is also
necessary for automated Configuration Management. The SEE will
enforce both internal standards (file formats, file contents, file and
tool accesses, development data collection, etc.) and external stan-
dards (e.g., compliance with MIL-STD-1679).
Standardization carries much weight in the aims of Ada. Ada is
intended to be a standard language across all DoD with neither subsets
nor dialects. A standard language support system is also envisioned.
Proposed benefits of these standardizations include user transporta-
bility, software transportability and reduced re-invention. SEE stan-
dardizations have similar virtues to promote higher productivity and
better software.
One important feature of the SEE is the standard data base struc-
ture, automatically provided and maintained. A typical benefit is the
transition of software from software developer to the Software Support
Activity (SSA). Although usually a tedious, expensive process it
becomes trivial when both developer and SSA have the software in
standardized SEE data bases throughout the different life cycle
phases.
2. Present Navy Efforts
MTASS
The Machine Transportable AN/UYK-20, AN/AYK-14 Support Software
(MTASS) is a set of tools for military software development, hosted on
several large commercial computers and targeted for the military com-
puters mentioned in its name as well as the AN/UYK-44. The tools are
cooperative in that the outputs of some are the inputs of others.
They are standardized in that they work the same way on the various
hosts and they provide a basic set of tools for all programmers of the
________________________________________

Anything would be worth a try

i.A complex software project can be managed like other mega projects of physical nature.
ii.S-Curve means less cost at Early Phase huge cost at Mid Phase and less cost at Late Phase.
iii.Uncertainty is lower at the beginning of SDLC but increases as the project progresses.
iv.The Incremental model is an evolutionary life cycle model combining Waterfall model and Prototyping model. True
v.Risk management is not an integral part of project management rather it is organization responsibility to handle it.
vi.Maintaining quality in a software project is the domain of Project manager only.
vii.Translating the customer requirements into technical specifications for the software project is one of the tasks of project initiation activity.
viii.Project scope determination exercise helps to identify the technology for creating the software product.
ix.Product scope change toward the end of the project life cycle cannot be accepted regardless of any reason/requirement.

This sounds very much like an assignment/coursework.

A consultant who evaluates systems development process in a company needs to investigate areas such as IS project identification, project selection process, IS planning document, systems development life cycle usage, and the utilization of project management methodologies.

What are some important considerations for each of these investigative areas?

Is the in the US?

Following are the Electives for the international trade. i want to know the best 7 electives among the following :

Logistics Management

Business Process reengineering and ERP

project management

Quality Management

Supply Chain Management

ICT for Business World

Strategic IT Management

Data warehousing and mining

Technology and product life cycle management.

Please help.. Thank You.

I am an MBA with an MA in International Management. My advise is to select a focus that complements that of your bachelor’s degree. I would also consider the industry in which I worked or wanted to work. For example, if you think your future lies in manufacturing, quality management is hot and is PLC.

The next thing I would do is take a careful look at the course offerings themselves. Try to imagine how useful any one course will actually be in that area of interest. Does the lesson plan offer any real substance in terms of what employers are currently seeking in the market? (see Monster or Dice).

I have a bias toward some combination of technology and International trade as well as supply chain – makes sense right? trade and supply chain. I am an SAP consultant and therefore I can say that ERP systems are critical to international firms. I would say however, that in an effort to get the biggest bang for the buck, I would assume my future employer would pay for my ERP training and that therefore, to maximize my MBA expenditure I would want to ensure it broadened my knowledge in ways not available elsewhere. Therefore, on that premise, PLC or PM or supply chain management would be excellent. I am surprised no finance electives are available. Good luck!

http://saplutions.net/default.aspx

We are looking for Oracle apps Functional and Techno Functional candidates to work in USA. This is a Urgent requirement.

Experience in Order Management module in Oracle applications is a must. Experience in EDI implementation is a plus.
Minimum 2 fulll life cycles exp. is required.
Working in a reputed companies is a plus.

Desired Profile :
Strong communication skills to effectively deal with various clients and multi-track teams.

Understanding of the project life cycle process to effectively manage a sub-team through the complexities of the business solution.

Must have atleast 4 years of experience in the desired technologies.

Must be a excellent team player and self-motivated.

Should have experience in the atleast two life cycles of project implementation.

Pls send your resumes to recruiterforerp@yahoo.com

maybe post this on craigslist or monster.com?

project management is largely the balancing of three tenets (the triple constraint) over the projects life cycle. What are these three tenets, that PMI endorses,give two factors for each tenet as they go through the balancing process over a lifecycle

Project Risk Management Tenet #1: Assess Early and Often
Project risk management must occur throughout the life cycle of the project. Uncertainties can be discovered at any time, while the relative probability and consequence of identified risks can change over time. For instance, the farther along a project goes into the schedule, the more likely you will lose team members to other efforts. In addition, the impact of poorly defined requirements will typically have a greater impact on project success in the latter stages of the project. It is imperative that the project team address uncertainty early and often, throughout the entire term of the project.

Project Risk Management Tenet #2: Build It into the Schedule
In order to adequately deal with uncertain events, the project schedule must include risk management activities. The project manager must ensure that risk assessment (identification and analysis) and response planning initiatives are a regular occurrence. Depending on the size, scope, and complexity of the project, risk reviews can either be an agenda item on the weekly review meeting or a bi-weekly review by itself. Either way, the project manager must incorporate consistent risk management mechanisms into the project schedule.

Project Risk Management Tenet #3: Communicate and Illustrate Ownership
The inherent uncertainty of risk events tend to make key stakeholders avoid the subject altogether. Therefore, it is up to the project manager to employ effective communications and clear ownership of risk elements. Potential risks need to be clearly identified and assessed, and accompanied by targeted, yet realistic, response strategies. Simply put, risk response strategies need to function as a rifle, not a shotgun. Also, the project leader must ensure that team members are properly aligned as owners for specific risk events. When key stakeholders know who to contact regarding a critical uncertainty, clear communication is better facilitated.

We have agile methodologies, system development life cycle, project management, or other practices to improve our programming capabilities in order to help us and our client as well.

But how would you define Modern Software Development based on your own definition?

Similar question has been asked on this URL (http://www.codinghorror.com/blog/archives/000643.html), so read that first to have some insights.

Well it basically depends upon ur reganizational structure and OFCOURSE on wht sort of clients you have.
First of all i personally dont believe in this Agile methodolies,a good Development cycle and Management is always very sound in which the analysis processes takes a lot.
but if u are into a small level company with small client and you dont looking forward to make any client permenant then Agile might work but if you want to give an impretion to client then follow STANDARD and do tell client which standards you are following it will give a good impration to you client and you organizational struture will evolve as well

in terms of "uncertainty" early in a project’s life cycle.
In project management.

Concepts can sound great on paper, but you don’t know how well they’ll actually do until they’re implemented and finished.

what does project planning usually come befpre analysis and design? what are are some of the methodologies commonly used for requirements elicitation? how can prototype be used? what are some metrics that can be used during the SDLC? list the various steps and applicable metrics. What are some reasons why systems fail?

basically, yoou desing the project to make sure all scopes of work are compleated. then you analixe what you have to work with and what you need. then you design the product or service. usually alot is looked at as to compertors and diffrent systems that can be used. i recomend doing a alpha or beta test at a site with a discounted price of service. systems fail becuse of poor design or to much design.