Week 10.1 – 14th April. 2021
This week we are asked to delve deeper into Agile Practice, and to get a better understanding of how important this method is, when applying it, especially to a large project and when working on commercial projects.
Project management skills, is what we have been asked to develop further, as this is what will be required in some of our up coming modules.
We are starting this week with a talk from Belinda Waldock who will show us, from looking at her professional experience as an Agile coach who supports SMEs, and helps them to adopt an Agile practice.
She explains; “the Agile Method evolved, because the Linear approach to creating software was not working, due to time constraints, projects were taking to long to complete, and when a project was finally finished, the client would not be happy as to much time had past, and what they wanted had changed.“
(Waldock, B. 2021)
She continues to explain, that from this action, it helped the new method of the Agile approach to be put into place. They adopted a new frame work which would work, with many iterative stages, they were as follows;
- Discussion
- Design
- Construct
From putting this method into action the client is sent this “little bit of software,” which keeps them happy as they are being kept in the loop and by doing so, feed back is given for the incremental changes, which helps to keep the project on track. From this the software developers has a clarified concept of things that need to be included, what can be scrapped, and what can be developed.
Just to note; this means the software developers would not have used up all there resources, or budget, which means they have the time and money left incase anything changed last minute or went wrong, they would still not be out of profit, or resources which is valuable to projects like this.
Process
This is what I have been putting into practice when working on the Trello board. Having everything laid out clearly which shows, what’s being worked on, what needs to be done, and what has been completed. This part of the process is actually really helping to guide me through this term, and allow me to keep organised with staying on top of the workload.
I suppose if we were analysing the Agile approach, we would think about the end goal been the marathon and all the sprints thats are in-between, are what makes up the marathon, so by just focusing on one sprint, we are closer to reaching the end result.
Types of Agile
The methodology that I am incorporating into my thoughts and my process is Kanban. An agile approach, which allows you to focus on one thing at a time, and by doing so, tasks for me seem to be completed a lot quicker.
Although I do still struggle sometimes, with spending too long on one area for example; practical, which leaves less time for reading or research. But I am working hard to keep enforcing this method into my practice.
Week 10.2 – 16th April. 2021
Envisioning ( Product Planning)
After watching Alcwyn Parkers video on envisioning, I feel I have a clearer idea of understanding the importance of product planning. From looking at his research into Kenneth Rubins ‘Essential Scrum‘, I have taken a deeper look into the meaning of envisioning through the magazine article ‘Envisioning Desirements,’ by Robert R Hoffman and Michael J McCloskey.
The goal of the Envisioning Desirements Method (EDM) is to develop a list of “things we could make now that will not rupture the procurement plan or the budget” and “things we can make and add in the future but that we must allow for now in the present build so that the system can be easily upgraded.”
(Hoffman and McCloskey 2013)
My translation of this quote is more simply put as; to build small things now, that won’t put them out of pocket, and which can easily be manipulated in the future.
They explain the reason for the change in the name, this helps them to find a way, by the using results from different human-centered technologies.
Human–centred is an approach that is used to design interactive systems, that are accessible and useful with a close focus on the users requirements. They research into their needs and find out what they specifically want.
Activities Required to Complete the Envisioning Process;
| Envision Activities (Product Planning) | ||
|---|---|---|
| INPUTS | OUTPUTS | |
| Initial Idea or Pivoted Idea | Product Vision (this needs to be explained in a single concise paragraph) | |
| Planning Horizon | Product Backlog | |
| Completion Date | Product Roadmap | |
| Budget/ Resource | Other Artefacts | |
| Confidence Threshold | ||
Week 10.3 – 18th April. 2021
Estimation
From following on with the scrum agile framework, we are asked to research into scrum estimation, and to look at; how to apply estimation techniques, to either our individual practices or how to incorporate them into a team project.
Alcwyn Parker’s video reveals that there are a few different agile techniques, that can be applied to your practice, but the key is to work out how much time you have to practice the techniques.
The Three principles are;
- How many features will be completed?
- When will they be done?
- How much will this cost?
My understanding of this process, is getting to know the skills and weaknesses of your team, and then re-evaluate the time it takes for them to complete a certain feature. Alcwyn quotes;
These techniques require practice but over time it is possible to hone your estimation skills to be more precise and accurate. In a team context, the more mature the team the easier it becomes to estimate how long units of development will take.
(Parker, A. 2021)
He continues to clarify the process; how to convert tasks from the backlog into story points?
This should have already been completed in the envisioning process.
But to go into more detail; Story points is a technique how to estimate, the time required for the task, from evaluating the PBI (product backlog item).
- The amount of work needed to carry out the task?
- How much risk and uncertainty are involved?
- How complicated is the task?
How to Apply to my practice?
If I incorporated this scrum estimation technique into my own practice, I think it would be quite straight forward, but that still depends on the project involved..?
I would like to think if I had to draw assets, for a game, game art, find sound, work out a logo, or work on basic animatics, I should be able to have a really good estimate on the time needed to create these parts, and with knowing the applications I use quite well, and being aware of how quickly they run.
Risk
I wouldn’t have thought there would be any, although the biggest thing that could hold up time is if the application that I choose, needs an update?
But this should not pop up, as I am constantly aware what Adobe Creative Cloud is like, as I have used many of the applications now, especially throughout Indie Game Dev. For this reason, I have advanced a lot more with my current applications, there by I am a lot quicker, and can put the above into action in a small time frame.
Complications – This wouldn’t apply for the things above, because I know where to look if I get stuck. Plus I always allow extra time for a new skill.
If for instance that I wanted to learn more about character rigging, although I have learnt how to create animatics, and a better idea of time frames, I don’t yet know anything about character rigging, thereby I would allow at least 8hours( 1 full working day) when working on a two week RI project.
This will help me stay on board with my smart goals when studying a new skill for one hour at a time, then taking a break and put into practice. By using this method, I can acquire a more thorough way of learning, which should aid my development in this area.
References
Parker, Alcwyn 2021 Envisioning. Available at : https://flex.falmouth.ac.uk/courses/911/pages/week-10-envisioning?module_item_id=49213 [accessed 16/04/21]
PARKER, Alcwyn 2021 Estimation. Available at : https://flex.falmouth.ac.uk/courses/911/pages/week-10-estimation?module_item_id=49214 [accessed 18/04/21]
Rubin, KS. (2013) Essential Scrum. Upper Saddle River, Munich [u.a.]: Addison-Wesley.
Waldock, B. 2015 Being Agile in Business: Discover faster, smarter, leaner ways to work. FT Press.
Waldock, B. 2021 Belinda Waldock on the Agile Movement and Practice. Available at : https://flex.falmouth.ac.uk/courses/911/pages/week-10-belinda-waldock-on-the-agile-movement-and-practice?module_item_id=49212 [accessed 15/04/21]
HOFFMAN, Robert R. and Michael McCloskey. 2013. ‘Envisioning Desirements‘ 28(4).
RALPHY GETS ANIMATED..? 