home.social

#agile — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #agile, aggregated by home.social.

  1. Cynefin doesn't solve any problem for you, it is instead a "lens" to look at the world through. It helps you sense where you're at with a problem and then make better decisions.

    - Clear: write down the plan and execute it.
    - Complicated: create a rough plan, start executing, and adapt. In Product Development this is the classical use of Scrum.
    - Complex: run an experiment and see what it tells you.
    - Chaotic: take action and contain the problem.
    - Confused: gather just enough information to sense which domain your problem is actually in, and then act from there.

    Which domain is your team's current work really in?

    agilepainrelief.com/glossary/c

  2. 🐐 The Future of Work: examining the costs, benefits, and geopolitical risks of offshoring, AI integration, remote or in-office models, and long-term delivery sustainability. Leaders reflecting on the current state of agility across different business models and grappling with operational challenges and opportunities facing organizations in the world of AI.

    A 75-minute breakout. No passive presentations. The afternoon consists of candid, facilitated exchanges between peers, building on morning insights and sharing hard-won operational advice. Attendees are active participants. Everyone is expected to bring questions, experience, and perspective to the discussion.

    GOAT is a volunteer-led initiative from Ottawa's tech community, and Agile Pain Relief has supported GOAT from day one.

    Thursday, November 26, Ottawa Conference and Event Centre. Tickets are $200, capped at 250 people.

    Agile Ottawa Inc

    goagiletour.ca/

  3. Разработка ПО с жёсткими ограничениями бюджета

    Есть множество проектов, в которых нужно разработать какое-либо ПО с жёсткими ограничениями по бюджету. Хочу поделиться своим методом работы с такими проектами. Это не серебряная пуля, но, думаю, мой опыт будет интересен. В основном такой подход я практикую для небольших проектов: срок разработки — до 14 месяцев, а общее количество участников команды — до 10 человек. Для более крупных проектов такой подход уже не подойдёт: сделать их бюджетно — совсем другая история. Сразу уточню границы. Речь не о ситуации, когда денег нет совсем, а о проекте, на который есть примерно 60–70% от необходимой суммы. Этот диапазон основан на моём личном опыте нескольких проектов, а не на универсальной формуле: конкретный результат зависит от системы, команды и ограничений заказчика. Размер возможной экономии сильно зависит от квалификации техлида проекта. Также рассказ будет о создании чего-то нового, когда нельзя просто переиспользовать предыдущий опыт и готовые наработки. Не все описанные шаги нужны для каждого проекта, но пропускать их стоит осознанно, а не потому, что на них якобы нет денег.

    habr.com/ru/articles/1103514/

    #тестирование #agile #разработка_по #прототипирование #управление_проектами #постановка_задач #ограниченный_бюджет

  4. Scrum is focused on building high-performing teams who build great products. Kanban improves the flow of work while building great products. In many cases, each approach can be used to complement and enhance the other.

    Scrum Better with Kanban puts the two together. Combine Kanban and Scrum to make the invisible visible. See exactly where bottlenecks are happening. Coordinate work continuously, not in endless meetings.

    Success with Scrum, Kanban, or other Agile comes in large part from self-discipline, focus, courage, respect, and willingness to experiment continuously. So the day is hands-on, grounded on neuroscience of learning and play. Focus on experiencing, not memorizing.

    Scrum Better with Kanban: November 13, live online, 9:00 AM to 5:00 PM Eastern.

    #Scrum #Agile

    agilepainrelief.com/courses/sc

  5. Impact Mapping by Gojko Adzic is on sale on Leanpub! Its suggested price is $10.00; get it for $7.00 with this coupon: leanpub.com/impact-mapping/c/L #agile #business_and_management #software #startups

  6. Companies are starting to fall into a trap, and it goes something like this, "Our partners/competitors/… are Agile, so we need to be Agile." Becoming Agile without a valid reason will harm your organization. I can't state that any simpler.

    In the '80s and '90s, rival manufacturers often visited Toyota plants, and Toyota was delighted to welcome them, because Toyota understood that even if their competition copied company practices, practices change. What competitors weren't copying was the culture that created the practices in the first place, and that's where the real value was. Thus we had Cargo Cult Lean at many North American manufacturers, and it didn't produce the results that companies were hoping for.

    We're seeing that again with Agile. It's not enough to become Agile and to copy Agile practices simply because your competitors are. Unless you develop a culture that creates its own practices, this will lead only to Cargo Cult Agile, and not a true Agile Organization.

    What was the real reason your organization went Agile?

    #Agile #Leadership

    agilepainrelief.com/blog/becau

Share on Mastodon

Enter the server where you have an account.