Introduction
Agile project delivery framework is an integral part of system development processes as it implores the entire requirements and objectives of system that include business analysis and requirement specification, design, programming and testing, and deployment. In agile project delivery framework, there are several number of small cycles referred to as sprints and each sprint is conceptualized into a type of small project consisting of its specific task-based activities that include a backlog as well as consisting of pre-defined design, implementation, testing and deployment steps (Whitaker, 2014).
In this paper, the discussions will culminate into how an agile delivery framework can be used to by home improvement store chain to build an e-Commerce Website for its customers and prospects. It will include a project schedule that includes at least 2 phases and 12 tasks under the agile delivery framework where significant aspects such as iterations, roles or tasks responsibilities of each task will be outlined. Note that iterations allow partial and systematic deliveries of tasks pertaining to needed features with the most important factor being user needs and feedback.
Project schedule
According to the project schedule plan, it should factors phases and pre-defined tasks that are need in order to achieve project deliverables. However, in this case, the created project schedule plan factors in a partial schedule of the entire agile development process and it includes only 4 phases and 29 tasks pertaining to ecommerce website development. The partial project schedule plan estimates the time that will be taken to achieve tasks of each phase as well as elaborating much information pertaining to all activities in addition to grouping all sprints in each step together.
It is important to note that the created schedule plan factors in the dynamism related to agile project development and it creates room for change status and timeline updates accordingly as well as analysis components. In addition, the developed project schedule has implored the added tasks factor, people responsible, start and end dates as well as progress status. The aspects responsible with schedule analysis are technology tools embedded in the project schedule plan software which automatically calculates and adjust data to the table.
Screenshot for a Project Schedule under the Agile Delivery Framework
![]()
Product vision and strategies to conduct the envisioning practice
A home improvement store chain that needs to build an e-Commerce Website for its customers and prospects should implore a system consisting of key features of e-Commerce Website. This features should allow aspects such as product description, product pricing and discount rate, home improvement tutorial videos, order and pickup scheduling, store location and store hours, and other similar features. Typically, the product should allow the home improvement store chain to offer all the outlined services over the internet.
The purpose of the system is to convert physical-based buy and sell activities involved between a customer and the trader to be accessible over computing resources while at the same time considering the speed, quality, flexibility, collaboration, and efficiency of the system. For instance, the system will help to optimize computing-related values such as the interconnected framework and emerging technologies such Internet of Things (IoT). In addition, product will also be used to increase the market presence by absorbing far-flung customers, implement digital marketing concepts, and partner with prospective stakeholders as well as provide quality services and efficient customer-based self-care tools. Another aspect related to the company amounts to deploying the system for peer-to-peer marketing strategies, collaboration with IT-Business tools, and data gathering and analysis techniques.
The strategies to conduct the envision practice are all provided by agile development methodology and they include aspects such as iterations, stories, collaboration, quality delivery, and flexibility. In the first place, iterations involves dividing large processes into small tasks with pre-define cycles and activities that are to be executed by a delegated group of individuals. This means that the group is able to work at each task professionally and which provide quick results at the shortest time in addition to embedding the features needed. Secondly, agile provide collaboration between system owners, users, and developers. This is very important as all flaws and difficulties are trade-off with the best alternative hence, increasing the quality, essence, and efficiency of the product (Holtsnider, 2016).
The main roles of the Agile project team
The main roles of the agile project team is evaluate the basic features of a product to develop a prototype, collaborate with client and final user on needed aspects, communicate on trade-offs, and ensure quality assurance as well as deliver the final product on time. At the beginning, the roles of the team should include prioritizing on the fundamental features of the product to a level that satisfies the client and final user. Secondly, the other roles of the team should include collaborating with the client and end user during design and implementation process on aspects that need to be changed in order to make the end product successful and complete. In addition, the team should also carry out proficient tests and performance checks in order to improve quality, embedded arising opportunities, and deliver the needed project on time.
On the issue pertaining to the product manager’s professional background, he should be from an IT field with robust experience in IT-business system project management skills as so as to allow software development facilitation, iteration management, and development of the scope of work.
How iteration works in this project
The iteration works in this project through sprints and every sprint represents a specific feature. Each sprint is planned solely and the team has to finish one sprint before descending onto the next sprint. The sprint backlog contains list of items that need to completed in order to achieve objectives of the sprint and participant who are involved in sprint planning include product manager, team, and owner. The sprint should actually take less than a month and daily briefing should consume not more than 30 minutes. For instance, order and pick-up scheduling sprint should be planned and all sprint backlog determined by all participants (Bittner & Spence, 2013).
At the end of each Sprint, the participants including end users must meet to display completed work and question must range on what can be done to improve the product. For example, after the four month period which involved executing tasks pertaining the order and pick up scheduling sprint, the review meeting should will be conducted in order to evaluate missing elements or where improvements can be embedded in the project. It specifies closure or initiation of new tasks within a sprint. This review meeting should take less than five hours. After clear reflections are performed and the sprint is deemed as complete, the sprint is closed and another iteration involving the next sprint should begin.
Story
A user story is an important aspect of agile delivery framework because it embedded requirements based on the end user’s perception. An agile delivery framework is based on developing user-oriented systems and the only way to understand user preferences is to implement user story strategies that provide information varying elements such as the type of user, what they want, and why they want it. For instance, ecommerce product may utilize user story to understand how end user want to navigate through the product menu and how they arrange their preferred shopping list in a catalogue.
Conclusion
In conclusion, agile delivery frameworks are iterative and incremental related methodologies that provide dynamic and robust approaches for developing user-centric products. Project scheduling under agile delivery framework is very difficult to estimate due to ever-changing scenarios but are efficient in time-boxing events or activities.
References
Bittner, K., & Spence, I. (2013). Managing iterative software development projects. Upper Saddle River, NJ: Addison-Wesley.
Holtsnider, B. (2016). Agile development & business goals: The six week solution. Burlington, MA: Morgan Kaufmann Publishers/Elsevier.
Kelly, A. (2016). Changing software development: Learning to be agile. Chichester, England: John Wiley.
Maximini, D. (2015). The Scrum Culture: Introducing Agile Methods in Organizations. Cham: Springer International Publishing.
Whitaker, K. (2014). Principles of software development leadership: Applying project management principles to Agile software development. Boston, MA: Course Technology.
jmj11o3
AgileDeliveryFramework1.docx
0
