IT Factor TEAM 84 DANI CASABLANCAS, JOHN CRENSHAW, MICHAEL LEONARD, JOHNNY LU, MINNA PRITCHARD, CHAD TUNNEL

Client Vision  Commercial use produce a website that attract sponsors, donors, and other prospective faculty members.  Sales sell an image on what the IT major offers and what you can learn.  Marketing to have an attractive, vibrant website. Draw the attention of any visitor.  Communications provide news and events for incoming students.

User Requirements  Minoriity and Women Presence  Representation throughout website  Informs clients about the “What” and “Why” of IT  What is IT?  Why should you be an IT student? At GSU?  Appealing, Cross-platform Mobile Website  Employs techniques found in DMMT  Tabs, Content Heirarchy, Content Flow

Screenshots Desktop View Mobile View

Technical Requirements  Managed using Agile Scrum methodology and KanBan (Trello)  Responsive on All Screens  Contain a logo or banner designed by the team to promote brand recognition  Coded in HTML5/CSS3 without using obsolete elements or methods  External CSS  Consistency across the site  Appropriate content  Pages load quickly and Function Correctly  Evidence that usability best practices have been implemented (DMMT)  Published to the team webserver provided  Utilize any Coding Software

Testing Procedures  To test our product we used W3C validator, to validate whether our HTML and CSS were working.  RWD validators and checkers specifically mattkersley.com/responsive, and responsive.victorcoulon.fr.  A webpage loader tester.  A responsive image validator.  We used a tool called Embed Responsively to add our video to our website.

What is Done?  We have completed everything in our Sprint 3 backlog, our plan for this Sprint was to create the content, create a tour video and finish the code testing.  We answered all the question we asked in our product backlog.

Challenges & Changes Technical Challenges  Designing prospective student page, having enough white space to make content flow.  Had to create a simple font hierarchy, we had to many custom fonts.  Making sure everything was responsive.  Getting the “back to the top button to work. Changes we would make…  We would make the site more handicap friendly.  We would also make the site more accessible to foreign visitors.  We would also like to add an "About the Creators” page.

Inspect  This last Sprint went smoothly, if there was communication problem it was discussed so there was no misunderstanding.  Communication  Group Me + Trello  Trello + Google Drive to prioritize our product.  Trello- A learning curve

Transparency  In the beginning to Daily Standups were helpful, but after a while they were just redundant. We all knew what our roles were and we communicated when we need to do.  Everyone knew what our end goal was, so it was easy to agree on what done looked like.  Done was having everything in our product backlog answered.

10 Lessons Learned Meeting outside of class gave us more opportunities for transparency Communication Constant site tests reduce the debugging time at the end. Testing By giving everyone equal tasks, we accomplished more, faster Work Plan Everyone has a speciality. Try a task outside of it. Challenging Skills Multiple brains have twice the power of one Asking for Help After a draft, let the product rest and look at it again Fresh Eyes If one method is not working, try a different one. Switch it Up Starting the sprint earlier gives more time for collaboration Earlier, Not Later Life happens. Be prepared to adapt when it does Flexibilty When the work grows dull, make it enjoyable. Enjoy It

Advice and Recommendations  For future teams we suggest that they stay in contact, at least check in twice a week with team members.  Instead of being assigned a topic it would be interesting to see what topic students come up with on there own.  Agile Scrum is convenient but the flaw in this was that students viewed this as a mock trial instead of a real world trial, other than that the methodology is flawless.