Introduction
In order to pass this assessment you have to have an example of using two complex techniques
NZQA lists complex techniques as the following:
• Agile, Kanban, or waterfall techniques
• version control
• collaboration and communication
• managing assets
• code review
• project scheduling.
NZQA lists complex techniques as the following:
• Agile, Kanban, or waterfall techniques
• version control
• collaboration and communication
• managing assets
• code review
• project scheduling.
Collecting Evidence
|
You will need to collect evidence of you using project management tools.
My recommendation is to take screenshots of before, during and after. This looks like the picture on the right. |
|
Version Control Software
|
Agile, Kanban or Waterfall
|
You will want to pick one of these three styles of development when making your project. This will also be helpful for when you are sitting the external.
Waterfall In the Waterfall approach, tasks are completed in a fixed sequence, like building a house—foundation, walls, then roof. Your Gantt chart could be used as evidence of this Agile In Agile, work is divided into small, iterative cycles, like updating a mobile app every two weeks based on user feedback. Your iteration cycles could be used as evidence of this. KanBan With Kanban, tasks are visualized and prioritized on a board, like using sticky notes to track progress on a whiteboard. A Trello scrum board could be used as evidence of this |
|
Collaboration and Communication
|
If you were to collaborate on a project and choose this as a technique I would evidence of the following
1.) Regular meetings with notes or KanBan shared board. 2.) Github version control software as a collaboration tool |
|
Managing Assets
|
If you were going to manage assets I would expect the following:
- Optimisation of assets used in the outcome - Good file naming - Good folder strutures - Github repository - Version control |
|
Code Review
|
Code review is when another developer checks your code to make sure it's correct, clear, and follows the rules, like a teacher marking homework to catch mistakes before it's shared with the class.
Example: A developer writes a login feature and asks a teammate to review it, who then suggests improving password validation to make it more secure. I would expect code review notes as evidence. |
|
Project Scheduling
|
Project scheduling is the process of planning and organizing tasks, timelines, and resources to ensure a project is completed on time. It includes setting deadlines, assigning responsibilities, and creating a timeline for activities. Example: When building a website, the project schedule might include: Week 1: Design the layout Week 2: Develop the homepage Week 3: Add features like login and contact forms Week 4: Test and launch the site This helps everyone know what to do and when to finish it. |
|
