Projects that have a short deadline, like in the case of the three-week timeline presented by Charlie Poole’s case study have very little flexibility due to the time restrictions. Not much can be changed in such a short period. The purpose of this article is to discuss the most important aspects that enhance the success of projects with a short period by advocating for a complete understanding of the project and knowing the capabilities and weaknesses of the team members in order to determine how duties are to be delegated and project goals attained.
Software Development Project Methodology Application in a Team
Software application building projects require the application of methodologies that work best, giving excellent results within the time frame provided for successful completion. Poole had to identify the best methodologies to apply within three weeks and also choose the best team leaders to facilitate the attainment of set objectives. Changes that lead to the achievement of set goals are crucial and must be adopted by all team members. Having a project management office that encourages all team members in the project to focus on the long-term objectives of a project is important and ensures commitment to the application of benefits realization management (Alexander, 2017). The benefits of the project should inform decision making through all the stages of the project lifecycle. In this case study, Poole had worked on the project for one year and identified that the pre-sales of the project were good, the client was happy with the application, the completion of the stories satisfactory, and weekly drops passed their tests. These results showed that the project was performing as expected and the accruing benefits good and required to be maintained.
With only three weeks to make a few changes, Poole realized that strengthening the teams in the project was the most crucial aspect of the project in order to have lasting effects even after leaving them. Having had a similar experience with a short term project with little time to make serious changes before exit, it is obvious to me that Poole required careful strategy execution. According to (Alexander, 2017), a project manager must be able to create linkages between strategy formulation and strategy execution through talent identification, team management, and appropriate allocation of resources. Poole managed to select the most suitable team leaders whom he had known over the one year in the project who would focus on the most important parts of the project that would generate the greatest value. This was an important decision since good team management is crucial in the success of any project. As explained by (El-Sofany, Alwadani, & Alwadani, 2014, pp. 1–6), project teams must have a clear direction and narrowed down objectives that are measurable with the members being able to trust each other and build relationships that are centered on behavioral and technical competence to meet project goals.
Team Management within Extreme Programming Methodology in the Short-run
One requires to have a good understanding of the methodologies to be used even if only at a theoretical level in order to implement plans that are simple and effective. It is not necessary to have had practical experience of such methodologies but knowing the requirement and implications of each prove crucial to making informed decisions of what to propose to the project teams. Poole had to use a methodology that would have the greatest positive impact on the project. Having studied extreme programming (XP), it was logical to select four methodologies that could be applied in a short time and have long-lasting effects. According to (McKay, n.d.), extreme programming attempts to reconcile man and productivity through the improvement of operational strategies to enhance software development through social change using unique software development techniques. Choosing to implement only four of the 12 extreme programming core practices was informed on the time available and the objectives to be met in three weeks as well as their implications in the long run.
Check this Article Out
What’s the advice about the Systems Development Life Cycle (SDLC) are to give to the aspiring Project manager?
Is Basecamp makes it simple to communicate and collaborate on projects?
Continuous Integration
Continuous integration is one of the core practices chosen by Poole. As explained by (Kupsch, Miller, Basupalli, & Burger, 2017), continuous integration allows codes to be stored in the central repository during software development that allows integration of all stages of development to identify bugs and remove them to reduce turnaround time and improve quality. This would have continued to enhance quality and avoid time wastage in the short term of the project by increasing coordination between the teams working on the project. The practice acts as a quality assurance measure.
Small Releases
Small releases were another core practice chosen by Poole. Since small releases involve providing customers with miniature versions of the product to gauge customer reactions and feedback, they help to determine the accuracy in which the project objectives are being met. (Yadav, Yasvi, & Shubhika, 2019) States that small releases allow for accountability and efficiency by dealing with customer feedback on errors and bugs and therefore minimizing risks. This was an important decision by Poole since the practice would ensure quality products even after leaving at the end of the three weeks.
Onsite Customer
Onsite customer is crucial where constant consultations have to be made. In this case, study, having onsite clients was crucial in order to implement small releases and obtain recommendations on necessary changes to enhance customer satisfaction. (Yadav, Yasvi, & Shubhika, 2019) explains that on-site customers help to resolve disputes and problems with software development at each stage leading to an improved product that meets customer needs.
Planning game
The planning game was the fourth practice identified for implementation. This allows for planning meetings and reviews of the software development project where the programmers and the customers can meet regularly and discuss the project’s plans and what has been achieved with reference to the objectives of the project (Yadav, Yasvi, & Shubhika, 2019). This strategy was important in sustaining customer satisfaction.
Improved Team Building
It is not true to say that one can do whatever it takes to get results because, in the long-run, good results achieved in the short-run may turn into liabilities in terms of sustainability, cost-effectiveness and innovation changes. Every decision and action must be carefully analyzed using well-founded methodologies based on theoretical principles and technical know-how. Communication is crucial in teams and is usually encouraged through regular meetings. Poole changed the weekly meeting from report-based meetings to discussion meetings where ideas could be exchanged, and accomplishments highlighted. This provided additional opportunities for brainstorming and finding solutions to problems that were being experienced and also boosted morale as team members identified the areas they were making progress. Feedback among team members and the project managers as well as with the clients provides a comprehensive information exchange that ensures effective communication during planning, execution, and review of a project (McKay, n.d.). This was followed by a selection of team leaders that could report to the project coordinator reducing the number of reports to be given by the group. (Alexander, 2017) Proposes that the training, development and mentoring of identified team leaders who are talented increases the probability of success and ensures increased commitment by team members in the attainment of the objectives of the project. This decision ensured that, even after Poole left the project, the team leaders would continue to implement the identified objectives successfully once they were fully empowered. This ensured increased team planning and identification of stories for the application and establishment of a more workable project structure.
Conclusion
Software development projects depend on the identification and empowering of a good team that is committed to the attainment of the project goals. Poole was able to identify the plans, methodologies, and resources needed to implement them within the given time. Understanding of the project facilitates decision making when choosing priorities to be given to those activities that would yield the best results with the identified team within the set time frame. Team building is crucial in software development projects and must be enhanced through continuous communication and feedback with the customers, management, and team members.
References
Alexander, M. (2017, September 1). Project management: 7 steps to on-time, on-budget, goal-based delivery. Retrieved November 4, 2019, from https://www.cio.com/article/2427972/article.html
El-Sofany, H. F., Alwadani, H. M., & Alwadani, A. (2014). Managing Virtual Team Work in IT Projects: Survey. International Journal of Advanced Corporate Learning (IJAC), 7(4), 1–6. https://doi.org/10.3991/ijac.v7i4.4018
Kupsch, J. A., Miller, B. P., Basupalli, V., & Burger, J. (2017). From continuous integration to continuous assurance. 2017 IEEE 28th Annual Software Technology Conference (STC). https://doi.org/10.1109/stc.2017.8234450
McKay, V. (n.d.). What is Extreme Programming? (XP). Retrieved November 3, 2019, from http://www.selectbs.com/process-maturity/what-is-extreme-programming
Yadav, K. S., Yasvi, M. A., & Shubhika. (2019, April 17). Review on Extreme Programming-XP. Retrieved November 6, 2019, from https://www.researchgate.net/publication/332465869_Review_On_Extreme_Programming-XP
Comments 2