5 Tips for Using Agile Development: Methods We Use for Re-launching a Website

February 18, 2016 by Drew Robison

So, you have decided to use agile methods to relaunch a site or complete a development project. It may seem daunting at first to understand all of the nuances of managing a project or developing applications using this method. However, rest assured there are tangible benefits to adopting agile application development. This incremental approach will allow the product owner as well as your development team to see progress on key value proposition components early in the project.  Because agile requires more testing throughout; you can produce a higher quality product. This guarantees improvement over the previous website. The end results are satisfied product owners and happy developers. To help you with adoptions here are five tips we picked up while re-launching websites using agile development.


1. Complete Buy in from All Stakeholders: In order for the process to work it has to be a part of the culture. It’s important to include intended end-users in the process as much as possible. When end-users are driving development, issues are recognized more quickly. Sometimes corporate bureaucracy dictates and C-level executives don’t see the benefit in taking time out of their day to have regular standups or status meetings. Overcome this by consistently presenting the values of the method up front. Value Examples; The early and continuous delivery of backlog satisfies the product owner and motivates the team. Developers and other departments work together in a way that builds applications that are dictated by the user. Read more values of agile application development.

2. Apply The Core Principles of Scrum: It’s important to remain flexible but also have structure. Scrum provides a framework for roles, steps, and responsibilities within the agile method. With the scrum framework, the scrum master keeps everyone on task while the product owner dictates development priority. During a website relaunch, product owners should evaluate the issues with the previous site when compiling and prioritizing backlog.

3. Stand During Daily Stand Ups: Actually standing during your daily stand-ups and using a task board to refer to keeps the speaker focused and straight to the point. This deters the team from trying to resolve issues on the spot. The point of the standup is primarily to give a quick status report. Schedule time to resolve the issue after the standup meeting. As you discover changes or new implementations that don’t aid in achieving your goal, don’t be afraid to give them the ax.

4. Engage in Mentorship: As team members learn, share and teach the rest of the team. This type of cross-mentoring keeps everyone on the same page. Each member now has more familiarity with the project as a whole.

5. Give Estimates in Story Points: Time estimates can be a real challenge. When approaching a large complex project, estimate on a macro level and report time in story points rather than actual time values. This will keep your estimates more accurate.


Blog post currently doesn't have any comments.
 Security code