<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 for developing software are becoming increasingly common in the workplace. To better prepare computer science students for the workforce, Agile concepts can be introduced into the classroom in courses such as Software Development or program capstones. However, current Agile tools do not lend themselves to use in academics. A new tool is necessary to bridge the gap between academics and industry. The goal of this research is to develop a tool that provides an introduction to Agile, Scrum, and other software development methodologies but is targeted towards short-term projects. The tool will increase team member responsibility to reduce the friction seen in group projects. Additionally, the tool will support instructors managing several disparate concurrent projects.
</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
The roadmap is currently in a state of transition as the project moves between research phases. As such, several categories are not filled at this time.
<aside> 🗺️ Features: This is the single source of truth for the feature roadmap.
</aside>
<aside> 🧪 Features: This is a periodic export of work in AIECode about AIECode. This feeds the roadmap
</aside>
Filtered Roadmap Views
Roadmap By Status (Kanban Style)
Roadmap By Topic (complete and incomplete)
Roadmap By Value (Incomplete only)
Roadmap By Priority (Incomplete Only)
This database describes each of the phases of the project by timeline and target audiences.
We are currently in Phase 5
Subpages