Term Paper on "Lessons Learned"

Term Paper 4 pages (1176 words) Sources: 0 Style: APA

[EXCERPT] . . . .

Right, What Went Wrong, and Why Introduction

The accelerating pace of product lifecycles, specifically in many high tech and software-dominated industries in conjunction with the increasing number of competitors in specific markets are bringing an high sense of urgency to software development. The three-week project as discussed in the readings recommended for this assignment provide a glimpse into transforming the principles of extreme programming into measurable results on software development projects. The core components of fine scale feedback, continuous process including integration, shared understanding, and programmer welfare all are foundational elements of the concept. When extreme programming is attempted in many organizations the organizations' culture often rebels however as these concepts are different than long-standing processes and perceptions of how time should be managed. From the readings from this assignment however it is clear that extreme programming can significantly change the perception of time itself in organizations, while underscoring the need for greater continuous improvement of applications to customers" requirements while constantly thinking more broadly than just the writing of code to see how the application will integrated into a broader workflow. This is a "forest from the trees" mentality that is essential for time to be perceived differently in companies attempting to use extreme programming to increase the efficiency of their development process.

Lessons Learned: What Went Right

Undertaking a three-week turnaround to a project forces first an entirely new mindset relative to the perception of time and risk in many organizations. This is a very positive aspect of attempting and completing projects with the three-week turnaround as it forces organizations to challenge their perceived limitations around project processes, dependencies and performance. Second, when time gets compressed and the objective of the project is clear, a very high level of collaboration takes place. Everyone on a project is looking to not only get their coding and product tasks done but also to help others. A race mentality can set in and teams begin competing against their old time estimates to get work done. The entire level of intensity goes up across a team and programmers work to get done more in less time as opposed to devoting more and more hours to the project. One of the foundational elements of extreme programming is programmer welfare and sustainable pace, and in the best-managed three-week project teams, collaboration becomes so fluid that everyone celebrates a milestone of every team. In addition, effective leaders in the middle of managing a three-week project needs to develop the mindset that emergencies are opportunities to show the entire team how effective collaboration can be in completing tasks. This is critical as it first takes care of the emergency, and second, binds the team to focus on quick resolution of issues vs. being entirely focused only on their aspect of the project.

In addition to the change in the perception of time and what is accomplishable there is also a change in how teams look at the broader use of the code they are creating. Three-week projects force an integration mindset into development teams and also make it clear that the integration points for the application, whether they are system or process-based, need to be ready for the release of the application within a very short time period. These integration points, in experiences gained on projects, can be as manually intensive as getting other software companies to write small code sets to ensure compatibility, to a broader set of programs that would be considered application integration adapters or connectors. A three-week project… READ MORE

How to Reference "Lessons Learned" Term Paper in a Bibliography

Related Term Papers:

Lessons Learned From Making of a Quagmire Essay

lessons learned from Making of a Quagmire by David Halberstam and apply it to the defacto American raj in Afghanistan. First is not to become too closely associated with a… read more

Essay 2 pages (728 words) Sources: 2 Topic: Military / Army / Navy / Marines

---

Negotiation Stories: Lessons Learned Professional Writing

Negotiation Stories: Lessons Learned

Negotiation is the framework upon which business and politics are able to function effectively (Tohm, 2001). There are three primary facets of negotiation which exist in… read more

Professional Writing 30 pages (9576 words) Sources: 20 Topic: Business / Corporations / E-commerce

---

Project Management A) Lessons Learned Sessions Essay

Project Management

a) Lessons learned sessions or conducting project-post mortems are essential for the success of future projects, because of two primary reasons: on one hand, they can allow the… read more

Essay 3 pages (1043 words) Sources: 7 Topic: Accounting / Auditing

---

Finance Lessons Learned in Finance Personal Term Paper

Finance

Lessons Learned in Finance

Personal and professional lessons learned and insights gained from studying finance are directly applicable to many decisions in everyday life. From balancing a checkbook to… read more

Term Paper 2 pages (524 words) Sources: 0 Style: APA Topic: Economics / Finance / Banking

---

Lessons Learned From the Love Canal Environmental Crisis Term Paper

history of Love Canal, the lessons learned, and the movement toward a proactive response to environmental protection.

The tragic experience of the Love Canal served as a catalyst for the… read more

Term Paper 8 pages (2327 words) Sources: 6 Topic: Environment / Conservation / Ecology

---

View 100+ more related papers  >>