Description
Assignment 4: How to Become a Leader in Agile Projects
Due Week 8 and worth
100 points
The following resources may be helpful when completing this
assignment:
- Adaptive Leadership (http://www.thoughtworks.com/sites/www.thoughtworks.com/files/files/adaptive-leadership-accelerating-enterprise-agility-jim-highsmith-thoughtworks.pdf)
- Agile Leadership and Coaching (Development Manager’s Need to grow up!) (http://lostechies.com/joeocampo/2007/05/15/agile-leadership-and-coaching-development-manager-s-need-to-grow-up/)
- Agile Project Management (http://www.ccpace.com/resources/documents/agileprojectmanagement.pdf)
- Situational Leadership for Agile Software Development. (http://www.luca.minudel.it/freestaff/situationalleadership.pdf)
- Team Empowerment (http://www.agile-process.org/team.html)
- The Agile Leader: Adaptability (http://www.mindtools.com/pages/article/newLDR_49.htm)
Write a four to five (4-5) page paper in which you:
- Explain how to handle the documentation needs in this project using the Agile concepts.
- Determine the necessary success factors one would need to become an Agile leader in this project which contains a complex scope and extended timeline.
- Recommend the approach to manage offshore resources in this project, and determine the associated challenges and mitigation strategies to ensure the success of the project.
- Suggest strategies on measuring the performance and quality of the products and services of this organization and provide the approach to accelerate the testing process.
- Use at least three (3) quality resources in this assignment. Note: Wikipedia and similar Websites do not qualify as quality resources.
- Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.
- Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.
Explanation & Answer
Attached.
Running HEAD: How to become an Agile leader.
HOW TO BECOME AN AGILE LEADER.
Running HEAD: How to become an Agile leader.
ABSTRACT.
The success of an agile project development entirely relies on a sophisticated agile leadership.
Proper Leadership does not just entail commands and delegation of tasks rather it is reflected
upon the results of the team members. An agile leader focuses on the needs of others,
acknowledge other ideas and give proper guidance as they aim at achieving their set targets. This
paper the agile documentation and how it can be handled effectively. It also attempts to
determine the success factors of one to be an agile leader for development of e-commerce
website. Its gives a clear indication of the management approaches of offshore resources, its
challenges and the possible solutions. This paper is finalized with strategies of performance and
quality improvement of product inclusive of an approach to improve the test processes.
Keywords: Agile leadership, e-commerce website
Running HEAD: How to become an Agile leader.
The agile software development framework typically values and prefers working
software to comprehensive documentation. An agile document is barely sufficient for a situation
at hand. It is a critical part of the software development projects. This concept is often perceived
by the agilest as a strategy that increases project risks hence requiring high level of efficiency
and sophistication when it comes to documentation (Rubin, Eran; Rubin, Hillel 2011). Agile
analysts have discovered that agile documentation encourages confusion and a waste of time but
that does not mean it is not required and should be eliminated. Documentation is only done when
it is concluded to be the most probable way of achieving the set goals of the development of
software project.
One of the best ways of handling documentation is preference of executable
specifications to static documents. Some of these documents captured as the executable
specifications include; requirement specifications and design or architecture specifications...