What is agile tasks list and why is it important to the projects?
Agile tasks list is a to-do list that represents the tasks needed to accomplish the user stores. People apply the agile tasks list to ensure quality of stores and manage the project easily (West,Grant, & D’silva, 2010) . Most students do not like to create the agile tasks list for their class projects. They think the agile tasks list is not necessary for the projects, so they do not want to spend time to think about how to create agile task list for their projects. However, after attended the Cisco Innovation Jam, I realized that creating the agile tasks list is very important. It is a very important practice and habit that students should have before graduation. In software development, most of requirements you get from your clients are just abstract ideas, and your job is to turn those abstract ideas into reality. For instance, my current project is developing the Facebook apps for small business owner. However, my clients did not have any ideas about what kind of apps that she wanted for her Facebook page. In this situation, I applied the agile tasks list with the Cisco Idea Generation Platform (Cisco Innovation Jam, 2014) to design the requirements for the project. First of all, I identify the audiences. The audiences for this Facebook page are the customers who need the services on nails and hair, then I came up with the idea to create Facebook apps to display my client’s nail art design, also the services and fees. People nowadays like to look the reviews and customer’s rating before purchasing any services. Therefore, The app can show my client work including the affordable price, it will help my client to promote her business and attract people when looking on her Facebook page. Now I have the user story, the next task is breaking down the user stores into many sub tasks, and this is how I did to my project.
How can I make my tasks to meet the “Done” definition in Agile and avoid the rework process?
In my experience, some of my classmates may misunderstand the “Done” definition. They thought that the user store would meet the “Done” if it has been fully implemented. However, that is not true. In order to meet the “Done” definition in Agile, we need to pass the all the test, especially the acceptance test from the product owner and client. (Grant, Gerush, & D’silva, 2012)
After failing several times to meet the “Done” definition in the project, my advice is to spend time communicating with your client and product owner. During the communication try to gather as many information as you can for the requirements. Try to come with specific question and listen carefully on the client’s answer. The other advice is trying to come with the prototype and show the client to collect feedbacks, so you can make sure that you are moving on the right direction or not.
Peer reviewed primary research: West, D., Grant, T., Gerush, M., & D’silva, D. (2010). Agile development: Mainstream adoption has changed agility. Forrester Research, 2, 41. Retrieved October 12, 2014, from http://bit.ly/11IwuUq
Peer reviewed secondary research: Vlaanderen, K., Jansen, S., Brinkkemper, S., & Jaspers, E. (2011). The agile requirements refinery: Applying SCRUM principles to software product management. Information and Software Technology, 53(1), 58-70.Retrieved October 12, 2014, from http://bit.ly/1v3sGnr
kienlamcs100w 