ALTERYX INSPIRE | Join us this May for for a multi-day virtual analytics + data science experience like no other! Register Now
2 Day Countdown - The Alteryx Community will be temporarily unavailable for a few hours due to scheduled maintenance starting on Thursday, April 22nd at 5pm MDT. Please plan accordingly.

Istanbul, TR

Connect with other users of Alteryx products in Istanbul. By joining this group, you gain access to those who regularly work with this software, pose questions, and discuss and share best practices and challenges.
Welcome & Guidelines

Find tips to make the most of your User Group experience.

This is an open group. Sign in and click the "Join Group" button to become a group member and start posting.

Stupid Things 2 Do with Self-Service Analytics 3 - Sticking to Waterfall

13 - Pulsar

Publisihed here;


Sticking to Waterfall Methodologies in Analytics Projects

Many organizations adopt the waterfall methodology while they’re democratizing analytics and BI. That is usually a mistake. Waterfall development is one of the critical reasons why tasks take too long and fall short of providing value. Also, longer waterfall cycles carry the risk of transitioning into bad code and application design mistakes that remain undiscovered until the project’s end.




Agile methodology offers a more viable solution. Agile development methods include shorter, incremental cycles, which allow malfunctions to happen first so that mistakes can be identified and fixed more quickly.




Agile development methods can be an ideal fit for many business applications where continuous refinements are expected. They’re particularly handy where applications need to consider new requirements and new data. If your analytics’ projects are moving slowly, you should analyze whether the traditional waterfall approach is the cause. The next step is to consider whether agile might be the right fit for your goals to expand analytics and BI throughout your organization.