1. Lecture 4: Main Build Management Damien Markey

2. Lecture 4: Main Build Management How to start a build Assembling the team –Designer –Developer –Database developer –System administrator –Project manager/Producer Roles/Responsibilities/Tasks

3. How to start a build First task –Re-evaluate scope and plan –Has it changed due to any of the following: the results of the prototype lab client requested changes Market changes Technology changes If so, re-scope and/or re-plan the project within the new boundaries

4. How to start a build - 2 Merge the visual designs and prototype layouts –Create a graphical template of main site pages –Go through “Cut up” of graphical template to create the HTML templates –These can be agreed and delivered to designers in batches to speed up production

6. Co-operative Development Practice Create, agree and publicise file-naming convention for the content –Common ones are Section_pagename_date_time.XXX Author_pagecode_date_time.XXX (where pagecode is the unique identifier of a page on a site) Agree page sign in and out procedures –Avoid two people working on the same page

7. Co-operative Development Practice -2 Create, agree and publicise folder structure for the site –Common examples include Images directory Script directory HTML directory ASP page directory So everyone knows where to find and store files they need

8. The Team This can already be identified by this point If not identified then key personnel need to be found Their roles and responsibilities have to be identified In many cases members of the team will share roles e.g. –the technical lead could be the programmer on a small project In this case you are the team!

9. The Team - 2 Roles within the team are in 1 of 3 categories –Essential Roles Roles without which it would be impossible to deliver even a small scale project –Secondary roles Roles that can be useful (even necessary) in mid to larger scale projects –EXpert roles Specialist roles that are needed on large or niche area projects

10. The ESX Rules Some examples of ESX roles –Essential – Project Manager Is required to scope and plan a project –Secondary – Programmer Can be needed to code JavaScript/ Flash/ CGI scripts but would not be needed on a brochure site –Expert – Security Expert Would be needed on a project for an online bank but not on a children's play site Larger projects can require Secondary/Expert skills

11. Typical Roles and Responsibilities Common roles within projects include Designers Information Architect CopywriterArtist QA lead Tester Audio/Video/3d/Streamin g Engineer Media Buyer Project Manager/Producer Account Manager Technical Lead Creative Lead Network Manager Security Expert Programmer Web integrator

12. Project Manager/Producer (E) Responsible for: –Scoping Project –Creating and maintaining Project Plan –Allocating and managing resources (including team) –Managing budget and timescales –Handles contract/legal issues Main point of contact for Client and team If no one else does, the PM has to!

13. Account Manager (S) Hangover from Advertising/Media agencies Liaises with Clients and understands their customer requirements –Acts as client representative to Internal team (usually PM and Creative lead) –Acts as team representative to Client Liaises with Client over several projects Mostly sales and marketing role Can be handled by PM on small projects

14. Technical Lead (E) Has the overall view of the technical aspect of a project Prepares technical strategy and briefs for PM Manages the programming and technical teams Allocates specialists (such as networking expert) for more specialised tasks Essential for all but the simples of projects

15. Creative Lead (E) Responsible for Creative concept and design for entire site Manages designers and artists Also responsible for allocating resources for specialist design tasks, such as 3D or animation tasks Liaises with technical lead, programmers and any technical specialist on feasibility of designs

16. Network Manager (S) Responsible for setting up, configuring and administrating: –web servers, –email servers –and any other agreed hardware necessary to fulfil the technical delivery of a project Can also be responsible for registering domain names and setting up net links Can be the Database administrator in small projects

17. Security Expert (X) Responsible for the creation of encryption plans and setting up financial transaction security Should have experience in this are with encryption technology Can recommend strategies and products Often a network engineer, database administrator or lead programmer Usually the best paid of them all!!!!

18. Programmer (S) Responsible for the development of applications on the site in a programming language –Usually specialists in one of the following Flash,CGI,JAVA,JavaScript,SQL,C/C++ –Usually has skills in two or more of above

19. Web Integrator (E) Responsible for the integration of visual designs and backend programming Usually codes the final HTML pages, integrating media and any client side programming into the pages Often the HTML guru and is the final person in the process before hand off to QA Often communicates directly with PM and Technical lead

20. Designers (E) Create the look and feel of a site Create the initial Graphical templates Often now create the basic HTML page using a tool such as Dreamweaver Has to have an understanding of digital design not just print/Fashion/graphical design On small projects can be the Creative Lead

21. Information Architect (S) Responsible for –Site Architecture –Site Navigation –Search/Data retrieval –Interaction design/User Experience Planning Also responsible for error messages, legal/Terms of Reference, privacy messages, users technical needs

22. Copywriter (S) In knowledge based sites responsible for extraction of knowledge form the subject expert Creates new copy Or Checks Client copy

23. Artist (E) Responsible for turning the designers creations into Web format –Decreasing resolution –Optimising images –Cutting up screens Nowadays the designer often performs this task

24. QA lead (E) Responsible for ensuring the site meets the scope and functionality requirements specified Interacts with programmers and designers during bug fixing to assist completion of the site Responsible for giving final “go-live” OK to PM

25. Tester (E) Part of QA team Responsible for the testing of site to ensure it meets functional and scope requirements specified On small teams can be the QA lead

26. Audio/Video/3d/ Streaming Engineer (X) Responsible for the creation of any of the above content types for delivery to the technical and creative leads

27. Media Buyer (X) Responsible for the advertising campaign –Both Offline Posters, Billboard, TV, Radio –And Online What banner and other ads will run on the site What ads will be run for the site and where –Responsible for any links to portals