Some #truths (again, and tuned):

- #Kanban origin is not #Agile
- “Board” does not exist in #Scrum theory
- Story Points come from #XP, not Scrum
- User Story is only a promise for conversation
- User Story doesn’t come from Scrum
- You should not compare #teams based on story points they finalize
- #Scrum is a #framework (not a method, not a #methodology)
- #Jira does not make you #Agile
- Scrum and Agile are different things
- #Scrumban is not what you think it is
- “Daily Stand-up” is not the right name in Scrum
- There is no minimum duration of a #Sprint in Scrum (could be 3 days, 9 days,...)
- There are no more “roles” in Scrum
- You can use Scrum and Kanban together (not Scrumban...)
- All events in Scrum are there to enable #inspection (with #transparency), so #team is able to #adapt
- #Frameworks implementations are not the goals
- There is no Scrum in SAFe, but a mix of ScrumXP
- #SAFe is not the only framework at scale...
- Scaling Agile will not work if your #organization does not know the basics
- #Certifications do not ensure you’ll be a good

They answered: Yes! Their impacts on software #startups are notable! The survey explored which #Kanban and #Scrum components are best suited for navigating #uncertainty and #ambiguity in a fast-paced environment.

For more details, you can see my master's thesis published here:

bth.diva-portal.org/smash/record.jsf?pid=diva2%3A1876897&dswid=776

در این پژوهش، بررسی کردیم که کدام مؤلفه‌های کانبان و اسکرام (به عنوان متدهای پرکاربرد اجایل) برای هدایت عدم قطعیت و ابهام در یک محیط توسعه محصول سریع مناسب هستند. از لینک بالا می‌توانید جزئیات بیشتر را در گزارش پایان‌نامه کارشناسی ارشد من مشاهده کنید.

instagram.com/1agilist
twitter.com/1agilist
@YekAgilist