Software projects often fail because people begin programming before fully understanding the problem or planning key activities. Projects are temporary endeavors with a defined beginning and end that create something new and unique, while operations are ongoing and repetitive processes that sustain existing systems and services. Other factors that distinguish projects from operations include levels of uncertainty versus predictability, disruption of the status quo, and amount of risk involved.

2. Why do software projects fail?
• People begin programming before they understand the
problem

3. planning controlling activities
achieve objectives complete an activity.

8. • Projects are:
• temporary - they have a definitive beginning and end
• unique - they are a new undertaking, unexplored ground

9. • Projects are characterized by:
• a new product, service or process that hasn't existed before to create new
value
• one objective to be achieved and once that's done, the project is
terminated
• systems having to be created
• performance, cost and time are uncertain
• upsetting the status quo and violate the established practice
• having more risks as they are usually done for the first time

10. •RiskVs Issues??

12. • repetitive - they have expected inputs and outputs every time
• ongoing - they have a continuous cycle of execution

13. • Operations are characterized by:
• repeat process, product or service to sustain the business
• multiple objectives to be achieved again and again
• systems already created and in use
• performance, cost and time are known
• supporting the status quo and sticks to the established practice
• having fewer risks as they are repeated many times

14. Project Operations
Temporary End-over Ongoing Routine
New Original Work RepetedWork
Unique Output Repetitive output
Terminated once objectives are
acchieved
Adopted new objectives
once achieved

15. •Does Software have operation work??