meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
ixc2024:tech:wfrontend:project_planning:start [2024/05/27 14:57] – rubenhuygensixc2024:tech:wfrontend:project_planning:start [2024/05/27 15:29] (current) – rubenhuygens
Line 2: Line 2:
 //Successful project planning is the backbone of any hackathon project.// //Successful project planning is the backbone of any hackathon project.//
  
-After coming up with an initial project idea, it is a good idea to think about how to ensure that there is a common understanding of your project (see //Documentation//). Moreover, it is important to structure your work going forward. You might want to assign certain roles to team members based on their strengths and set deadlines so that you ensure all of your work is finished in time (see //Team work//).+After coming up with an initial project idea, it is a good idea to think about how to ensure that there is a common understanding of your project (see //Ideation//). Moreover, it is important to structure your work going forward. You might want to assign certain roles to team members based on their strengths and set deadlines so that you ensure all of your work is finished in time (see //Team work//).
  
-=== Documentation ===+=== Ideation ===
  
    * **Think Like a User**: Put yourself in the shoes of your target audience. What are their needs? What problems are they facing? This will not only help you think of the appropriate use cases, but it will also help you get on the same page as your teammates.    * **Think Like a User**: Put yourself in the shoes of your target audience. What are their needs? What problems are they facing? This will not only help you think of the appropriate use cases, but it will also help you get on the same page as your teammates.
    * **Keep It Simple:** Start with a minimum viable product (MVP). Focus on the core features that solve the primary problem. Additional features can be added later if time allows.    * **Keep It Simple:** Start with a minimum viable product (MVP). Focus on the core features that solve the primary problem. Additional features can be added later if time allows.
-   * **Create user stories** User stories are documented features, described from the perspective of users. They should be formulated in the following structure:+   * **Create user stories** User stories are documented features, described from the perspective of users. They should be formulated in the structure below. 
 +      * **Prioritize:** The most efficient and standardized way to formulate user stories is with the MoSCoW method. MoSCoW stands for //m//ust, //s//hould, //c//ould, //w//ould. Each category reflects a larger importance, such that //must// features should be implemented long before //could// features.
  
-  As a [user], I [must/should/could/would] be able to [feature](, such that [goal])+  As a [user], I [must/should/could/would] be able to [feature], so that I can [goal].
  
-   * **Prioritize:** The most efficient and standardized way to formulate user stories is with the MoSCoW method. MoSCoW stands for //m//ust, //s//hould, //c//ould, //w//ould. Each category reflects a larger importance, such that //must// features should be implemented long before //could// features.+__See also:__\\ 
 +{{:ixc2024:tech:wfrontend:project_planning:user-story-examples-word-doc.png?400|}} 
  
-__Example User Stories:__ +   * **Wireframing**: See [[ixc2024:tech:wfrontend:project_planning:wireframing|Wireframing]] for more information 
-{{:ixc2024:tech:wfrontend:project_planning:user-story-examples-word-doc.png?600|}} +      * **Start with creating Low-Fidelity Wireframes:** Use pen and paper or simple online tools to sketch basic layouts. Focus on the //flow and structure// rather than details. 
 +      * **Iterate Quickly:** Share your wireframes with teammates and get feedback. Make quick adjustments based on input. 
 +      * **Move to High-Fidelity Designs:** Once the structure is finalized, use tools like [[https://www.figma.com/|Figma]] or [[https://helpx.adobe.com/support/xd.html|Adobe XD]] to create detailed designs with actual UI components.
  
 === Team work === === Team work ===
- +   * **Use Agile Methodology:** Break your project into small, manageable tasks (sprints). Regularly review progress and adjust plans as needed. 
- +      * **Define sprints**: A sprint is a period in which a work is done to reach a final product. Before each sprint, it is decided what the final product should look like. We suggested defining daily sprints. 
- **2. Create wireframes**  +      * **Stand-ups**: Stand-ups are short explanations of each team member of what their work will be for the foreseeable future. This ensures that the whole team is up to date and that no time is wasted due to misunderstandings. 
- +   * **Assign Roles and Responsibilities:** Clearly define who is responsible for what. This helps prevent overlap, ensures accountability, and plays into every team member’s strengths. 
- +   * **Use management tools**: The use of management tools takes saves significant time, which is highly important in the amount of time available for this project. 
- +      * **[[https://trello.com/| Trello]]**: Trello allows you to categorize User Stories, such that members can assign features to implementers and the progress status of features can easily be viewed. This takes some of the mental load off the leader's shoulders and provides a reference for all team members. 
-\\ +      * **[[https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects|GitHub Projects]]**: GitHub Projects is a feature that helps you organize and manage tasks, issues, and pull requests within a GitHub repository, providing a visual way to track progress and collaborate on projects. It allows you to create task boards, automate workflows, and prioritize work efficiently. This assumes some knowledge about GitHub, so it is only recommended if the whole team has experience with git.
-\\ +
- +
-- **Start with Low-Fidelity Wireframes:** Use pen and paper or simple online tools to sketch basic layouts. Focus on the //**flow and structure**// rather than details. +
- +
-\\ +
-\\ +
- +
-- **Iterate Quickly:** Share your wireframes with teammates and get feedback. Make quick adjustments based on input. +
- +
-\\ +
-\\ +
- +
-- **Move to High-Fidelity Designs:** Once the structure is finalized, use tools like **Figma or Balsamiq** to create detailed designs with actual UI components. +
- +
-\\ +
-\\ +
- +
- +
-** Tools for Wireframing: ** +
- +
-\\ +
-[[https://www.figma.com/|Figma]]\\ +
-[[https://helpx.adobe.com/support/xd.html|Adobe XD]]\\ +
- +
-\\ +
-\\ +
- +
-**3. Project Management** +
-\\ +
-\\ +
- +
-**Pro Tips:** +
-\\ +
-\\ +
- +
-- **Use Agile Methodology:** Break your project into small, manageable tasks (sprints). Regularly review progress and adjust plans as needed. +
-\\ +
-\\ +
- +
-- **Assign Roles and Responsibilities:** Clearly define who is responsible for what. This helps prevent overlap and ensures accountability. +
-\\ +
-\\ +
- +
-- **Daily Standups:** Have brief daily meetings to discuss progress, blockers, and next steps. This keeps everyone on the same page and identifies issues early. +
- +
-\\ +
-\\ +
- +
- +
-**//Project Management Tools://** +
- +
-\\ +
- +
-[[https://trello.com/| Trello: Simple, visual task management.]] +
-\\ +
-[[https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects|GitHub Projects: Integrated with your codebase.]] +
-\\ +
-\\ +
- +
-**4. Version Control with Git** +
-\\ +
-\\ +
- +
-**Pro Tips:** +
- +
-- **Use Branches:** Create a new branch for each feature or bug fix. This keeps your main branch clean and makes it easier to manage changes.  +
-\\ +
-\\ +
- +
-- **Commit Often:** Make small, frequent commits with clear messages. This makes it easier to track changes and revert if necessary. +
-\\ +
-\\ +
- +
-- **Pull Requests (PRs):** Use PRs to review code before merging. This helps catch issues early and ensures high code quality. +
-\\ +
-\\ +
- +
- +
-Resources: +
- +
-[[https://github.com/apps/github-learning-lab|GitHub Learning Lab]]+