Iteration 7
- Iteration Goals
- Iteration Roles
- Iteration Current Tasks
- Screenshots before Iteration
- Screenshots after Iteration
- Accumulated Completion Points
- Iteration Conclusion
- Project Summary
Improve the website's User Experience and fix any bugs found.
- Ihab & Netanel as the Backend development team.
- Ruby & Dan as the Frontend development team.
- Open Issues
- HuBoard - Visual Issues Board
- Server routes for renovation edit - Points: 21
- Profile page fixes - Points: 13
- Home page fixes - Points: 13
- Code Cleanup - Points: 13
- Home page content - Points: 13
- Statistics Data - Points: 13
- Search Engine Optimizations (SEO) - Points: 8
- Status page integration - Points: 13
- Organization's Google Account - Points: 13
- Dashboard finishing touches - Points: 21
Total: 141
Completed: 141
- Completed:
- created Server routes for editing renovations
- Profile page bug fixes
- Home page bug fixes
- Code Cleanup
- Created JSON file containing initial home page content
- Contacted Client and retrieved required statistics data for production
- Added site title & description as part of Search Engine Optimizations
- Integrated status page into home page
- Created the Organization's Google Account to hold all the API keys
- Removed redundant dashboard features that were canceled
- Additionally:
- Updated developer's manual with additional information
- Changes the website overall style
- Made the website more responsive
This project was a great adventure for all of us. Four hardworking students with a passion for programming combining forces to help an Organization that already does so much for the community. Right from the start we saw that the team was divided to Frontend and Backend naturally and we never had to argue about who will do what. The Leader of our group was Netanel Draiman, a hardworking, smart and professional programmer. When we had our doubts and worries - he helped us and made sure we are on track. We worked as a group from the beginning until the end. Now you can see the fruits our project bore. We are satisfied with the result and we hope to get together again for many projects in the future.
The way we planned our development Process was:
- Planning the features we need to develop
- Develop the barebone of the project to get a firm grasp of what our abilities are
- Add more needed features without concerns about UX for maximum efficiency
- Make sure the Client does not want any new features or changes. if he does, sit and plan to make sure it does not hurt the timeline.
- Fix bugs and clean up code
- In the time left - make UX as best you can
Our conclusions from this projects are as followed:
- Make the iterations a little bit shorter, but not too short - when the iterations were 2 weeks or more, people began to slack off. when they were too short - people became stressed.
- Make sure to check up on the other teammates in short intervals - some team members need a guiding hand to make sure they always work when they have the time to do so. in such a short period of time, every minute is vital.
- Don't bite off more than you can chew - we needed to spread the work in a different way. we ended up working on too many "heavy" tasks at one iteration and then working on a lot of "light" tasks on another iteration. we needed more balance in the spread of tasks.
The 3 most important lessons from this course were:
- Bureaucracy is a pain - no offense to the course itself, but given the limited time scope of the project and the fact we had to do it while studying, we felt like we could achieve much much more if we had less forms to write and less "home exercises" to do. we spend about 40% of the time we had writing forms and iteration conclusions instead of doing actual work. Those formal tasks are good as a lesson, maybe, but they will not help the client at all and were a waste of precious time.
- The Client knows best - we met with our client before we started working and again after 2 months of work. between those 2 meetings a lot changed in the client's demands and in our understanding. As programmers, we tend to think about functionality and about a programmer's user experience and we tend to forget what the client really needs. its important to listen to the client and make sure you understand him exactly the way he means you to.
- Challenge yourself, no matter the price - in this project we learned the hard way that sometimes you cant just push work on the teammate who "knows best". Yes, the product is important, but it doesn't mean there is no time to learn how to do things properly. The optimal situation is: you face a new problem you never encountered - you search Google and ask for help but don't give up and let someone else pick it up where you left off. its important to solve the problem yourself, no matter how time it takes.