For New Zealand secondary students undertaking a significant Digital Technologies Project
Introduction
NZQA Scholarship Technology (93601) is not about producing the most technically Complex product. Instead, it assesses your ability to demonstrate sophisticated Technological practice, Justify your decisions, critically Reflect on your process, and show how knowledge, skills, ideas, and methods have been integrated to produce an innovative Outcome.
For Digital Technologies students, this means developing a substantial Digital Outcome such as:
- A software application
- A web platform
- An AI-assisted solution
- A game
- An information System
- An embedded System
- A mobile app
- A cybersecurity tool
- A Data analysis platform
- A digital service for a real client or community
The strongest submissions tell a compelling story of Technological practice rather than simply documenting coding activities.
Understanding What Scholarship Examiners Want
The assessment schedule identifies three major areas:
1. Synthesis and Integration
You must demonstrate how you combined:
- Technical knowledge
- Research
- Stakeholder Feedback
- Design thinking
- Testing
- Technological Modelling
- Development methodologies
into a coherent Outcome.
Outstanding candidates demonstrate both:
- Elegance (optimisation, polish, simplicity)
- Originality (innovation and inventiveness)
Digital Technologies Example
Rather than creating a Basic attendance System:
- Integrate QR code scanning
- Develop a database backend
- Automate reporting
- Design dashboards
- Implement authentication
- Gather Stakeholder Feedback from teachers and students
2. Justification
Examiners want clear evidence of why you made decisions.
Not:
“I used Python.”
But:
“Python was selected because it enabled rapid development, had appropriate libraries for Data visualisation, and could be maintained by future student developers.”
You should Justify:
- Languages selected
- Frameworks used
- Architecture decisions
- User interface Design
- Security choices
- Testing strategies
- Database structures
- Project management approaches
Outstanding candidates convincingly Explain both:
- Why their process was appropriate
- Why their Outcome addresses the identified problem
3. Critical Reflection
Reflection is often the difference between Scholarship and Outstanding Scholarship.
Outstanding candidates:
- Examine their own practice critically
- Learn from failures
- Compare alternative approaches
- Reflect on Technological practice in wider contexts
- Consider future developments and implications
Weak Reflection
“Testing showed a Bug which I fixed.”
Strong Reflection
“Functional Testing revealed the System architecture created unnecessary database queries. Refactoring improved Performance and highlighted the importance of considering scalability earlier in the development process.”
Choosing a Strong Project
The best projects typically involve:
Real Need
A genuine problem with genuine users.
Examples:
- School booking System
- Sports team management platform
- Cultural heritage archive
- Learning Support application
- Student wellbeing tool
- Community volunteer management System
Genuine Stakeholders
You should work closely with:
- Teachers
- Students
- Sports coaches
- Community groups
- Small businesses
- Cultural organisations
Stakeholder interaction should occur throughout development.
Appropriate Complexity
Scholarship projects should contain meaningful complexity such as:
Technical
- APIs
- Databases
- Authentication
- Machine learning
- Data processing
- Embedded systems
Human
- Multiple user groups
- Accessibility requirements
- Ethical considerations
- Privacy concerns
System
- Interconnected components
- Scalability
- Security
Recommended Project Structure
Phase 1: Identify the Issue
Define:
- The Need
- The stakeholders
- The Context
- Existing solutions
- Limitations of current approaches
Evidence:
- Interviews
- Surveys
- Observations
- Background research
Phase 2: Explore Possibilities
Investigate:
- Similar products
- Technical approaches
- Suitable technologies
- Constraints
Consider multiple options before selecting one.
Evidence:
- Comparative tables
- Prototype screenshots
- Research summaries
Phase 3: Plan Your Solution
Develop:
- Functional requirements
- Non-functional requirements
- User stories
- System architecture
Evidence:
- Wireframes
- Flowcharts
- ER diagrams
- UML diagrams
Phase 4: Develop and Test
Use iterative development.
For each cycle:
- Build
- Test
- Gather Feedback
- Refine
- Document Reasoning
Evidence:
- Code screenshots
- Testing results
- Stakeholder Feedback
- Version history
Phase 5: Evaluate
Evaluate against:
Functional Success
Does it work?
User Requirements
Does it solve the problem?
Fitness for Purpose
Does it work in the intended Environment?
Future Development
What could be improved?
Scholarship Report Writing Tips
Focus on Thinking, Not Activities
Avoid:
“I created the login page.”
Instead:
“A secure authentication System was required because stakeholders identified privacy concerns when storing sensitive student information.”
Show Decision-Making
Scholarship is largely about:
- Why
- Why not
- What changed
- What was learned
rather than:
- What happened
Tell the Story of Development
Your report should read like a narrative:
Problem → Research → Decisions → Development → Reflection → Outcome
Not:
Week 1 → Week 2 → Week 3
What Outstanding Scholarship Looks Like
The assessment schedule describes Outstanding work as demonstrating:
- Sophisticated synthesis and integration
- Innovation
- Optimisation
- Independent critical reflection
- Convincing communication
In practice this means:
Outstanding Candidates
- Solve authentic problems
- Adapt and change direction when necessary
- Use Stakeholder Feedback extensively
- Critically evaluate their own assumptions
- Demonstrate significant independence
- Present a polished final Outcome
Common Mistakes
Too Much Technical Description
Avoid pages of code explanation.
Focus on:
- Decisions
- Justifications
- Reflections
Limited Stakeholder Input
Stakeholders should appear throughout the Project, not just at the beginning and end.
Reflection Added at the End
Reflection should occur continuously.
Document:
- Failures
- Changes
- Learning
- Reconsidered decisions
Choosing a Project That’s Too Small
A Basic website or simple game rarely provides sufficient depth.
Your Project should create opportunities for:
- Complexity
- Evaluation
- Iteration
- Innovation
Suggested Digital Technologies Scholarship Topics
School and Education
- AI study assistant
- Assessment tracking System
- Student analytics dashboard
- Learning management extension
Community
- Volunteer management platform
- Community resource finder
- Local history archive
Wellbeing
- Sports Performance tracking
- Student wellbeing application
- Peer mentoring platform
Emerging Technologies
- AI-powered tools
- Machine learning classification systems
- IoT monitoring systems
- Embedded smart devices
Final Advice
The strongest Scholarship Technology submissions are not produced by the best programmers. They are produced by students who can clearly demonstrate:
- A significant authentic technological problem
- Sophisticated Technological practice
- Well-justified decision-making
- Ongoing Stakeholder engagement
- Deep critical reflection
- An innovative and effective Outcome
Think like a professional digital technology developer and designer who can Explain, Justify, evaluate, and improve every decision made throughout the Project. That is the mindset that leads to Scholarship and Outstanding Scholarship.
