DZone
Agile Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Agile Zone > Top 9 Ways to Speed Up Your Development Process

Top 9 Ways to Speed Up Your Development Process

Yaniv Yehuda talks about the Forbes Technology Council's nine solid ways to speed up your development process.

Yaniv Yehuda user avatar by
Yaniv Yehuda
·
Apr. 26, 16 · Agile Zone · Opinion
Like (5)
Save
Tweet
12.58K Views

Join the DZone community and get the full member experience.

Join For Free

These days, it seems as if all tech teams share one missing component: time. It’s for this reason that I found it worthwhile to take a few minutes to summarize nine key tips shared by successful executives from Forbes Technology Council.

Here are their suggestions for keeping development moving forward quickly:

  1. Customize Agile Processes
    Yesterday, we discussed the value that banks are finding in using agile management. According to Satyam Tyagi (Certes Networks), delivering business value early should be your focus. Agile management allows a team to start delivering after the first “sprint”, correct mistakes early, adapt to changing needs and provides continuous value to customers.
  2. Work with Small Teams and Small Components
    Smaller teams delivering small components and micro services deliver quickly according to Venkat Rangan (Clari Inc). When combined with systematic tests and integration, agile allows small teams to break down the larger problem and accomplish their goals more quickly.
  3. Challenge your plan
    At Space150, Marc Jensen and his team incorporate a “Challenge Phase” that allows them to clarify the end goal, discuss the problem and define project success before they even start.
  4. Stick to Deliverables
    While change requests and bugs are inevitable, Jonathan Penny (Myfootpath), recommends not delaying development on any issues not related to a bug or a security issue. Ship deliverables on time and other changes can be made in a future sprint, he says.
  5. Change Management
    Guillermo Ramos has learned an important lesson from his time at Greatist, “There are three things to consider: scope, resources and time. Changing any one of these will affect the other two.” Increasing scope will inevitably slow down the development process without simultaneously increasing resources. The same holds true if there is a decrease in resources without a decrease in scope.
  6. Development Sprints
    Thomas Griffin (OptinMonster) is a big believer of utilizing development sprints to keep the pace charging ahead. Quick wins keep the team focused and energized.
  7. Reduce Scope “Creep”
    As VP of Technology at Voices.com, Chris Kirby has come to learn that scope creep is the enemy of teams trying to get deliverables out on time. Breaking things down into smaller phases allows for critical elements to be completed first and long term requirements to be put off until there is a lull in development.
  8. Utilize the Lean Approach
    “The key to moving quickly and effectively is to build your product in small increments, test with real users in real-life situations ASAP, and then adjust your direction based on their feedback and your data/observations.” -Jim Walsh, GlobalLogic

Download our free white paper: Continuous Delivery Best Practices and Essential Tools

Use Continuous Integration

For those unfamiliar, this software continuously runs tests and deployments as code is updated. Yusuf Simonson from the Muse believes that this forces engineers to be more scrupulous in their testing and verification.

agile CI/CD

Published at DZone with permission of Yaniv Yehuda, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Evolving Domain-Specific Languages
  • Refactoring Java Application: Object-Oriented And Functional Approaches
  • How to Minimize Software Development Cost
  • Upsert in SQL: What Is an Upsert, and When Should You Use One?

Comments

Agile Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo