PM jobs in Technical Industries.
Project planning. What is the single most important quality for a PM to have? What is the single most important quality for a PM to have? The Art of Project Management: Success | The Slalom Blog. March 21, 2013 by Carl M. Manello Carl Manello A victorious army opposed to a routed one, is as a pound’s weight placed in the scale against a single grain. —Sun Tzu, military strategist While I won’t compare weights and measures of ancient China (the “I” and the “SHU” versus the pound and the ounce), I will measure up Sun Tzu’s comment against the weight of managing a successful project.
All too often projects are focused on the future. The drive for success is what becomes important! Like a victorious army, a project team which is in a state of accomplishment, recognition and celebration for what they have delivered will be more successful than one which plods along unsung and unrecognized. I have no beef with Waterfall methods. Too often, project teams reflect on their successes (or missteps) only after the project has been completed. Like this: Like Loading...
Project Initiation. SWOT analysis. A SWOT analysis, with its four elements in a 2×2 matrix. A SWOT analysis (alternatively SWOT matrix) is a structured planning method used to evaluate the strengths, weaknesses, opportunities and threats involved in a project or in a business venture. A SWOT analysis can be carried out for a product, place, industry or person. It involves specifying the objective of the business venture or project and identifying the internal and external factors that are favorable and unfavorable to achieve that objective. Some authors credit SWOT to Albert Humphrey, who led a convention at the Stanford Research Institute (now SRI International) in the 1960s and 1970s using data from Fortune 500 companies.[1][2] However, Humphrey himself does not claim the creation of SWOT, and the origins remain obscure.
The degree to which the internal environment of the firm matches with the external environment is expressed by the concept of strategic fit. Matching and converting[edit] Use[edit] Strategy building[edit] Regression testing. The intent of regression testing is to ensure that a change such as those mentioned above has not introduced new faults.[1] One of the main reasons for regression testing is to determine whether a change in one part of the software affects other parts of the software.[2] Common methods of regression testing include rerunning previously completed tests and checking whether program behavior has changed and whether previously fixed faults have re-emerged. Regression testing can be performed to test a system efficiently by systematically selecting the appropriate minimum set of tests needed to adequately cover a particular change. Background[edit] Experience has shown that as software is fixed, emergence of new and/or reemergence of old faults is quite common.
Sometimes reemergence occurs because a fix gets lost through poor revision control practices (or simple human error in revision control). Regression testing is an integral part of the extreme programming software development method. Effort versus Duration versus Elapsed Time (PMP CONCEPT 16) This is our sixteenth post in our new learning series: PMP Concepts Each post within this series will present a comparison of common concepts that appear on the PMP and CAPM exams. Effort versus Duration versus Elapsed Time During the “Estimate Activity Durations” process, the effort, duration, and elapsed time are determined for the schedule activities. Effort Effort is the number of work units required to complete the activity. Duration Duration is the total time to complete the activities based on the resources available to the project. Elapsed Time Elapsed time is the calendar time or span required to complete the activities based on the resources available.
Example Installing the new drip system for the landscaping is estimated to take 80 hours of effort. If there is one worker committed to 40 hours per week, the duration would be 10 workdays. However, if there are two workers each committed to 40 hours per week, the duration would be 5 workdays. Summary Effort is the number of work units.