<aside> 👉 Warning: This site has not been updated (for the most part) since 2022 and needs major review.
</aside>
https://indify.co/widgets/live/button/32oIzaOFaPypNqDOufrt
<aside> ✍️ If you are logged into a Notion account, you can make comments throughout! Please do!
</aside>
<aside> 🕶️ Toggle dark/light mode with cmd/ctrl+shift+L.
</aside>
<aside> ☎️ If you want to ask me a question or receive period updates on my research, please Contact Me here.
</aside>
🔗 Outside links
Agile Burndown - Phase 1 tool
AIECode Prototype - Phase 2
Phase 2 code repository [requires access]
User Stories, Persona's and Bugs [requires access]
AIECode ✨ - Phase 4 tool
Phase 4 code repository [requires access]
<aside> 📉 Agile and Scrum methodologies are now standard in software development workplaces. To properly prepare computer science students for industry, Agile concepts should be integrated into classroom settings, particularly in Software Development courses and program capstones. Current industry Agile tools, however, are not well-suited for academic environments.
This research focuses on developing a specialized tool that bridges the gap between academic and industry needs. The tool introduces students to Agile, Scrum, and other software development methodologies while being specifically designed for the short-term projects typical in classroom settings.
Key benefits of this tool include:
The tool's development is based on information gathered during Fall 2021, with implementation and testing in Fall 2022 to current.
</aside>
Agile: A software development methodology utilizing an iterative process of planning, developing and evaluating with a focus on collaboration.
Scrum: An Agile framework that more clearly defines the iterations and more formalizing how collaboration is performed.
AIE: Shortcut acronym used to reference the tool being developed by this project. Stands for Agile in Education.
Quick question and answer information about Agile in Education.
The Mission statement and vision statement for the project. These aspects should be kept in mind at all times.
<aside> 👉 These are some initial observations based only on the analysis of the survey results and are subject to change as further analysis is completed.
See Phase 3+4 Data Collection Plan for Data Collection details
</aside>
4.0 Developing for the user: The tool had a significant (positive) impact on students developing with the user in mind
5.1 Time spent maintaining: Students spent less time updating the status of work with the new tool and spent about the same amount of time creating work
5.2 Task creation from user stories: There were less students finding it easy or difficult to create work and more students falling into the ideal middle
1.2 Knowledge outcomes: While the tool had a significant impact on the perceived project outcome, other measurements showed no significant changes
6.1 First Delivery of code: There was not a significant change in the perceived delivery of working code
1.1 Daily Scrum: The tool’s guidance on daily scrum meetings did not improve the learning experience
Subpages