5 Solutions to Common Agile Web Development Project Pitfalls

This is my first LinkedIn Published Article. As a Web Developer with a decade of experience in the field, I figured it's time to share my knowledge and experience with the public. My target audience is anyone involved with Web Projects; From Business Owners & Project Managers to Graphic Designers & Web Developers, as well as anyone starting out in the field.

1. Understanding the Roles

There are many different ways to phrase these roles. I choose these for simplicity.

Client: Entity that requests the website to be created or redesigned.  At the end of day, one way or another, the client writes the paycheck and thus, what the client wants, the client gets. 

Project Manager: Entity that is the go between the Web Developer, Graphics, and Client. Project Manager must ensure Developer and Graphics get the assets needed to create the Website, as well as manage any hurdles that come about. Managing expectations, setting deadlines, and choosing options provided by the Web Developer in "tight deadline situations" ensures the website is delivered in manner that makes the client happy.

Graphics Designer: Entity that creates mockups, icons, logos, and the graphical assets of the website. Works with developer to ensure the design and mockups created can be implemented in time.

Web Developer: Entity that writes code to implement and create the website; Turns the mockup into fully functioning website. Creates options when there are time deadlines that Project Manager and graphics must decide on to ensure delivery of web project.

Quality Assurance: Entity that checks the website on a Development or Integration Environment to ensure quality before it goes live to Production.

Sometimes people have different titles, sometimes people have to wear two hats and have multiple roles. The important part is that each of these roles and duties are accounted for and each person knows what the other person is doing within the team.

Solution: Everyone understanding there own roles along with there team members roles.

2. Missing Assets - Logo, Images, Mockups, Text

In an Agile Environment, it's typical for the Developer not to get all assets at the start of a project. The client is writing text, and using Lorum Ipsum is usually a solution until final content is written. Once the project comes to fruition, many times last minute changes are required.  Sometimes Responsive Web Design is an afterthought when it should really be Mobile First.

Solution: Make sure to include the Developer from the start of the project in both meeting and during graphic of the mockup for the site. This will ensure that assets that will come later will be accounted for and that the design itself is feasible to create within the deadline given. Also make sure that Project Manager communicates to client that all assets for site are delivered in time in order to be implemented before site goes live.

2. Communication - Web Developer and Deadlines

The unique aspect of Web Development, and Software Engineering in general, is that, as humans, we live in a world with "Infinite Shades of All Colors" when communicating with people. But when it comes down to writing code, web developers specifically deal in "black and white." Web Developers must make thousands of "black and white" decisions when writing code.

It's one thing to talk about a cool new feature, another thing to design cool new feature, and a completely "black and white" thing to implement cool new feature into the website.  

The Web Developer needs to have the technical skill, experience, and communication skills to be able to break down a project into components when building the website. If there is a tight deadline, it's up to the Web Developer to create options that will enable the project to be completed in time.

Solution: Web Developer must be able to know how to modify the "game plan" in such a way that reduces time needed to create website. This needs to be done in way that is clearly communicated and accepted by Project Manager and Graphics, and usually involves creating a number of options in how to modify the game plan. Keeping an open line of communication between Project Management, Graphics, and Web Developer is very important in this regard.

3. Expectations

There should be two types of expectations. The first is "delivering the project," and the second is "going above and beyond." 

If the expectation to begin with is "going above and beyond," then this removes a motivating factor for the people in the project; As one can't go "above and beyond" if that itself is the expectation.

Solution: Team members must have a Base Game Plan, and if time allows a "Above and Beyond" game plan. Client should only be aware of Base Game Plan. This is known as "Under Promise, Over Deliver."

4. SEO is wrong, or ignored

This should be part of assets; Work with client to ensure SEO elements, from meta descriptions, to h1-h6 placement, to microdata & JSON-LD, are received.

Solution: Light but strongly Client education is needed here to explain why this is important. This gives client opportunity to analysis to what extent SEO is needed during creation of Web Project.

5. Responsive Web Design As An Afterthought

There needs to be mock ups for iPhone width design, iPad width design, and Desktop width design. In that order. Developer must ensure site is truly responsive across all devices by testing it on all devices.

Using an emulator during development accounts for the "look" of the website in a mobile device; But one must actually use the mobile device to ensure the "look and feel" is correct. 

Solution: Know your target audience. If 50% of visitors use iPhone width devices to view website, go mobile first. Typically, one uses Google Analytics to analysis this, as well as analysis the Target Goal of the website to determine importance of Mobile Audience. Mobile is only going growing and going mobile first ensures the end result looks good on iPhone, iPad, and Desktop.