Recommended
More Related Content
Similar to Manual de sobrevivência do desenvolvimento web Drupal Day 2017
Similar to Manual de sobrevivência do desenvolvimento web Drupal Day 2017 (20)
Recently uploaded
Recently uploaded (20)
Manual de sobrevivência do desenvolvimento web Drupal Day 2017
- 1. Manual de sobrevivência do desenvolvimento web Drupal Day 2017
- 2. About me Ricardo Marcelino ricardo.marcelino@omibee.com Design background UI / UX Drupalist Project management Omibee CEO
- 3. Good ol’ internet Hypertext Frontpage Google Macromedia Flash Drupal, Wordpress Youtube and Social Apps and js frontend SAAS sites
- 4. Power to the user Digital documents Easier to edit Searchable Multimedia Blogs and Web 2.0 Cats and friends Connected services DIY
- 5. “We need a new website”
- 7. How to fail less Don’t skip discovery Generic requests without specs will hurt everyone. Align expectations Start by the end What’s the value you’ll be creating to the end users. Your client is not the audience User experience What will be the journey for each persona Tech solution The tools you’ll need based in what you’ve found Development Multi-disciplinary, working closely Release quickly and often (MVP is your friend)
- 8. Discovery
- 9. Discovery Strategy Goals, Messaging User Experience Audience, User journeys, Functionality and Usability Content Types, Management and Localisation Creative Look & feel, Assets, Brand Guidelines and Tone Development URL, Hosting, Legacy integration, Security and Development preferences
- 10. Estimations
- 11. Estimations Fixed quote + uncertainty = pain T&M allows bigger flexibility and work quality MVP is your friend Value based pricing vs value for money Communication and expectations alignment
- 12. Development
- 13. Development The right solutions for the solution Out-of-the box vs custom Feature creep Development is perceived as slow and expensive Code quality (Q&A)
- 14. Release
- 15. Release Did the client sign off the release? Are we delivering on time? Are we meeting the goals? Help the client to succeed. Measure and iterate A new beginning Security and support
Editor's Notes
- User Experience Audience – Who are we trying to communicate to? Who are your primary/secondary/tertiary audiences? Why? Is that different from your desired audience? What are their demographics? Why would they come to visit? When do they come? Why would they come back? User journeys – Who are the users of the site? What are their different needs? What do we want them to do? What are the current barriers? How can we increase customer satisfaction? How can we generate loyalty? How can we drive conversion? Functionality – What types of functionality beyond static content pages is required? Browser detection? Geo-IP detection? Multilingual support? Shopping cart or eCommerce? Data capture? Forms? Print screen? Cookies? Dynamic content? Interactive maps? Store locators? Blogs? Events calendar? Jobs listings? A feed for frequently updated content? A photo gallery? Social integration? Why is it needed? How will this functionality achieve our business objectives? Usability – What are the requirements for us to do user testing? What devices are we supporting? What browsers are we supporting? What platforms are we building for? What is the minimum screen size we should develop for each? What are the requirements and standards for accessibility compliance? Content Types – What is the content we will load into the site? Is it repurposing old content or creating new content? How many sections of content will there be? What pages are required? What are the different content types we need to support? Why is it needed? What will it achieve? How will the content be meshed together? How does the content relate to other content? Management –Who will write it? When will it be ready? Who will load content onto the site? Who will maintain it? What workflow and permission levels, approvals are required? Localisation – How many markets need to be supported? How many different languages within those markets? What are the content differences between different markets? When do the different markets need to be launched? What other market specific requirements should we be aware of? Creative Look & feel – What creative have you seen that you like? What don’t we like? Why? Assets – What branding work has already been done? How popular is it internally and externally with customers? Where can we find brand assets – logos, brand guidelines, photography? Brand Guidelines – How well defined are the brand guidelines? How rigid is the existing style guide? Tone – Are there existing websites that you like that would provide creative insight into a desired look and feel? Is there an emotional end-state we’d like to have your audience walk away with? Technical URL – What is the URL for this site? Who is the current domain registrar? How will we support multilingual markets? Hosting – Who is hosting the site? IIS or Apache Linux or Windows or other? What is the current load on the server? Are databases being used, if so, what type? Are there database preferences? What backup mechanisms are required? Will there be spikes in traffic requiring a content delivery network (CDN) like AWS, Akamai or Limelight? Legacy integration – What existing systems will this website need to connect with? Security – Will we need to create user accounts? Will encryption be required? Will there be password-protected areas? What personal data will we need to store and secure? Development preferences – Can we use Drupal? Is there a development framework we need to use? What devices, browsers and platforms need support? Tracking – What are the KPI’s? Will we track using analytic tools like Webtrends, Google Analytics or other measurement technologies like ClickTale or something more comprehensive like Adobe SiteCatalyst? Project Management Process – How does this project relate to other live projects? What’s the project plan? What are we going to do (Statement of Work)? What is the running order for activities (methodology)? When (timing plan)? How much will it cost (budget)? Communication – Can we use Podio? Is there other required communication channels to use? Who needs to be involved, when? What tools will we use to communicate, collaborate and share? Governance – How are we going to manage the process? Who are the stakeholders? Who’s responsible, accountable, consulted informed? How will we manage any changes in requirements? Approval process – How will we effectively manage the project team and the stakeholders throughout the project lifecycle? Project management – How are we tracking progress to ensure we’re meeting the defined requirements, running on time, and keeping to budget? When is the deadline for live date? Why? What is driving the requirement to meet that date?
- User Experience Audience – Who are we trying to communicate to? Who are your primary/secondary/tertiary audiences? Why? Is that different from your desired audience? What are their demographics? Why would they come to visit? When do they come? Why would they come back? User journeys – Who are the users of the site? What are their different needs? What do we want them to do? What are the current barriers? How can we increase customer satisfaction? How can we generate loyalty? How can we drive conversion? Functionality – What types of functionality beyond static content pages is required? Browser detection? Geo-IP detection? Multilingual support? Shopping cart or eCommerce? Data capture? Forms? Print screen? Cookies? Dynamic content? Interactive maps? Store locators? Blogs? Events calendar? Jobs listings? A feed for frequently updated content? A photo gallery? Social integration? Why is it needed? How will this functionality achieve our business objectives? Usability – What are the requirements for us to do user testing? What devices are we supporting? What browsers are we supporting? What platforms are we building for? What is the minimum screen size we should develop for each? What are the requirements and standards for accessibility compliance? Content Types – What is the content we will load into the site? Is it repurposing old content or creating new content? How many sections of content will there be? What pages are required? What are the different content types we need to support? Why is it needed? What will it achieve? How will the content be meshed together? How does the content relate to other content? Management –Who will write it? When will it be ready? Who will load content onto the site? Who will maintain it? What workflow and permission levels, approvals are required? Localisation – How many markets need to be supported? How many different languages within those markets? What are the content differences between different markets? When do the different markets need to be launched? What other market specific requirements should we be aware of? Creative Look & feel – What creative have you seen that you like? What don’t we like? Why? Assets – What branding work has already been done? How popular is it internally and externally with customers? Where can we find brand assets – logos, brand guidelines, photography? Brand Guidelines – How well defined are the brand guidelines? How rigid is the existing style guide? Tone – Are there existing websites that you like that would provide creative insight into a desired look and feel? Is there an emotional end-state we’d like to have your audience walk away with? Technical URL – What is the URL for this site? Who is the current domain registrar? How will we support multilingual markets? Hosting – Who is hosting the site? IIS or Apache Linux or Windows or other? What is the current load on the server? Are databases being used, if so, what type? Are there database preferences? What backup mechanisms are required? Will there be spikes in traffic requiring a content delivery network (CDN) like AWS, Akamai or Limelight? Legacy integration – What existing systems will this website need to connect with? Security – Will we need to create user accounts? Will encryption be required? Will there be password-protected areas? What personal data will we need to store and secure? Development preferences – Can we use Drupal? Is there a development framework we need to use? What devices, browsers and platforms need support? Tracking – What are the KPI’s? Will we track using analytic tools like Webtrends, Google Analytics or other measurement technologies like ClickTale or something more comprehensive like Adobe SiteCatalyst? Project Management Process – How does this project relate to other live projects? What’s the project plan? What are we going to do (Statement of Work)? What is the running order for activities (methodology)? When (timing plan)? How much will it cost (budget)? Communication – Can we use Podio? Is there other required communication channels to use? Who needs to be involved, when? What tools will we use to communicate, collaborate and share? Governance – How are we going to manage the process? Who are the stakeholders? Who’s responsible, accountable, consulted informed? How will we manage any changes in requirements? Approval process – How will we effectively manage the project team and the stakeholders throughout the project lifecycle? Project management – How are we tracking progress to ensure we’re meeting the defined requirements, running on time, and keeping to budget? When is the deadline for live date? Why? What is driving the requirement to meet that date?
- User Experience Audience – Who are we trying to communicate to? Who are your primary/secondary/tertiary audiences? Why? Is that different from your desired audience? What are their demographics? Why would they come to visit? When do they come? Why would they come back? User journeys – Who are the users of the site? What are their different needs? What do we want them to do? What are the current barriers? How can we increase customer satisfaction? How can we generate loyalty? How can we drive conversion? Functionality – What types of functionality beyond static content pages is required? Browser detection? Geo-IP detection? Multilingual support? Shopping cart or eCommerce? Data capture? Forms? Print screen? Cookies? Dynamic content? Interactive maps? Store locators? Blogs? Events calendar? Jobs listings? A feed for frequently updated content? A photo gallery? Social integration? Why is it needed? How will this functionality achieve our business objectives? Usability – What are the requirements for us to do user testing? What devices are we supporting? What browsers are we supporting? What platforms are we building for? What is the minimum screen size we should develop for each? What are the requirements and standards for accessibility compliance? Content Types – What is the content we will load into the site? Is it repurposing old content or creating new content? How many sections of content will there be? What pages are required? What are the different content types we need to support? Why is it needed? What will it achieve? How will the content be meshed together? How does the content relate to other content? Management –Who will write it? When will it be ready? Who will load content onto the site? Who will maintain it? What workflow and permission levels, approvals are required? Localisation – How many markets need to be supported? How many different languages within those markets? What are the content differences between different markets? When do the different markets need to be launched? What other market specific requirements should we be aware of? Creative Look & feel – What creative have you seen that you like? What don’t we like? Why? Assets – What branding work has already been done? How popular is it internally and externally with customers? Where can we find brand assets – logos, brand guidelines, photography? Brand Guidelines – How well defined are the brand guidelines? How rigid is the existing style guide? Tone – Are there existing websites that you like that would provide creative insight into a desired look and feel? Is there an emotional end-state we’d like to have your audience walk away with? Technical URL – What is the URL for this site? Who is the current domain registrar? How will we support multilingual markets? Hosting – Who is hosting the site? IIS or Apache Linux or Windows or other? What is the current load on the server? Are databases being used, if so, what type? Are there database preferences? What backup mechanisms are required? Will there be spikes in traffic requiring a content delivery network (CDN) like AWS, Akamai or Limelight? Legacy integration – What existing systems will this website need to connect with? Security – Will we need to create user accounts? Will encryption be required? Will there be password-protected areas? What personal data will we need to store and secure? Development preferences – Can we use Drupal? Is there a development framework we need to use? What devices, browsers and platforms need support? Tracking – What are the KPI’s? Will we track using analytic tools like Webtrends, Google Analytics or other measurement technologies like ClickTale or something more comprehensive like Adobe SiteCatalyst? Project Management Process – How does this project relate to other live projects? What’s the project plan? What are we going to do (Statement of Work)? What is the running order for activities (methodology)? When (timing plan)? How much will it cost (budget)? Communication – Can we use Podio? Is there other required communication channels to use? Who needs to be involved, when? What tools will we use to communicate, collaborate and share? Governance – How are we going to manage the process? Who are the stakeholders? Who’s responsible, accountable, consulted informed? How will we manage any changes in requirements? Approval process – How will we effectively manage the project team and the stakeholders throughout the project lifecycle? Project management – How are we tracking progress to ensure we’re meeting the defined requirements, running on time, and keeping to budget? When is the deadline for live date? Why? What is driving the requirement to meet that date?
- User Experience Audience – Who are we trying to communicate to? Who are your primary/secondary/tertiary audiences? Why? Is that different from your desired audience? What are their demographics? Why would they come to visit? When do they come? Why would they come back? User journeys – Who are the users of the site? What are their different needs? What do we want them to do? What are the current barriers? How can we increase customer satisfaction? How can we generate loyalty? How can we drive conversion? Functionality – What types of functionality beyond static content pages is required? Browser detection? Geo-IP detection? Multilingual support? Shopping cart or eCommerce? Data capture? Forms? Print screen? Cookies? Dynamic content? Interactive maps? Store locators? Blogs? Events calendar? Jobs listings? A feed for frequently updated content? A photo gallery? Social integration? Why is it needed? How will this functionality achieve our business objectives? Usability – What are the requirements for us to do user testing? What devices are we supporting? What browsers are we supporting? What platforms are we building for? What is the minimum screen size we should develop for each? What are the requirements and standards for accessibility compliance? Content Types – What is the content we will load into the site? Is it repurposing old content or creating new content? How many sections of content will there be? What pages are required? What are the different content types we need to support? Why is it needed? What will it achieve? How will the content be meshed together? How does the content relate to other content? Management –Who will write it? When will it be ready? Who will load content onto the site? Who will maintain it? What workflow and permission levels, approvals are required? Localisation – How many markets need to be supported? How many different languages within those markets? What are the content differences between different markets? When do the different markets need to be launched? What other market specific requirements should we be aware of? Creative Look & feel – What creative have you seen that you like? What don’t we like? Why? Assets – What branding work has already been done? How popular is it internally and externally with customers? Where can we find brand assets – logos, brand guidelines, photography? Brand Guidelines – How well defined are the brand guidelines? How rigid is the existing style guide? Tone – Are there existing websites that you like that would provide creative insight into a desired look and feel? Is there an emotional end-state we’d like to have your audience walk away with? Technical URL – What is the URL for this site? Who is the current domain registrar? How will we support multilingual markets? Hosting – Who is hosting the site? IIS or Apache Linux or Windows or other? What is the current load on the server? Are databases being used, if so, what type? Are there database preferences? What backup mechanisms are required? Will there be spikes in traffic requiring a content delivery network (CDN) like AWS, Akamai or Limelight? Legacy integration – What existing systems will this website need to connect with? Security – Will we need to create user accounts? Will encryption be required? Will there be password-protected areas? What personal data will we need to store and secure? Development preferences – Can we use Drupal? Is there a development framework we need to use? What devices, browsers and platforms need support? Tracking – What are the KPI’s? Will we track using analytic tools like Webtrends, Google Analytics or other measurement technologies like ClickTale or something more comprehensive like Adobe SiteCatalyst? Project Management Process – How does this project relate to other live projects? What’s the project plan? What are we going to do (Statement of Work)? What is the running order for activities (methodology)? When (timing plan)? How much will it cost (budget)? Communication – Can we use Podio? Is there other required communication channels to use? Who needs to be involved, when? What tools will we use to communicate, collaborate and share? Governance – How are we going to manage the process? Who are the stakeholders? Who’s responsible, accountable, consulted informed? How will we manage any changes in requirements? Approval process – How will we effectively manage the project team and the stakeholders throughout the project lifecycle? Project management – How are we tracking progress to ensure we’re meeting the defined requirements, running on time, and keeping to budget? When is the deadline for live date? Why? What is driving the requirement to meet that date?