menu
techminis

A naukri.com initiative

google-web-stories
Home

>

Agile Methodology News

Agile Methodology News

source image

Dev

1M

read

90

img
dot

Image Credit: Dev

Anonymous Feedback in Retros: When, Why, and How

  • Psychological safety and power dynamics are important factors in giving feedback during retrospectives.
  • Anonymous feedback allows team members to bring up important issues without hesitation.
  • Different types of feedback require different levels of privacy, and flexibility is key.
  • Implementing anonymous feedback can lead to increased participation, better addressing of sensitive topics, and the gradual building of trust.

Read Full Article

like

5 Likes

source image

Medium

1M

read

338

img
dot

Image Credit: Medium

Less Hunting for Information, More Coding: Why Integrated Repositories Matter

  • Context switching, or jumping between tasks and tools, hinders productivity in software development.
  • Integrated repositories help to eliminate the need for constant switching and provide a single source of truth.
  • Having all relevant information in a repo saves time and improves team collaboration.
  • By keeping everything in the repo, you create a centralized location for user stories, research, and project roadmaps.

Read Full Article

like

20 Likes

source image

Dev

1M

read

397

img
dot

Image Credit: Dev

Life of Become part of the team

  • In 2024, the author learned valuable lessons in Playwright, TypeScript, CI/CD Pipelines, and Selenium, enhancing their technical expertise and problem-solving skills.
  • Joining a new team required effective communication and time management for collaboration across different countries and time zones.
  • The author diversified their skill set by familiarizing themselves with iOS and Android testing for mobile applications.
  • Contributing to process improvement and navigating retrospectives were fulfilling experiences that fostered team growth and continuous improvement.

Read Full Article

like

23 Likes

source image

Alvinashcraft

1M

read

429

img
dot

Image Credit: Alvinashcraft

Dew Drop – January 6, 2024 (#4335)

  • Uno Platform has made progress in allowing devs to use Dev Gallery code cross-platform.
  • Artificial intelligence is expected to drive technological advances in 2025.
  • The AI-Ready Isolator++ API claims to be the first API which allows sites to be built that are interactive and use AI.
  • Microsoft's new Microsoft.Extensions.AI service allows OpenAI models to be called from C#.
  • Brady Gaster discusses .NET app upgrades in episode 331 of the Azure & DevOps Podcast.
  • Brad Smith, president of Microsoft, has said the US has a "golden opportunity" to lead in AI as the nation has a combination of talent, capital and infrastructure.
  • Mastering Peak Software Development Efficiency with Docker.
  • Detecting Browser Zoom Changes in JavaScript and Measuring the Distance Between Two Points with the Pythagorean Theorem.
  • JasperFx Software in 2025.
  • See What WebAssembly Can Do in 2025.

Read Full Article

like

25 Likes

source image

Scrum-Master-Toolbox

1M

read

4

img
dot

Ellen Grove: Managing Change in Complex Organizational Cultures

  • Ellen Grove reflects on her experiences as a Scrum Master facing resistance to Scrum in her organization.
  • She shares lessons on handling external resistance, managing personal expectations, and avoiding emotional burnout.
  • Ellen emphasizes the importance of focusing on what can be influenced and detaching from outcomes beyond one's control.
  • Maintaining focus and resilience when dealing with resistance to Scrum is crucial.

Read Full Article

like

Like

source image

Medium

1M

read

339

img
dot

Image Credit: Medium

Why VSM and the Product Operating Model Matter

  • The adoption of a Product Operating Model and Value Stream Management (VSM) can help organizations prioritize work, optimize workflows, and deliver maximum value.
  • A product operating model allows teams to focus on specific products, become experts, and manage the product's lifecycle. VSM complements this by optimizing workflows to deliver value.
  • Both models emphasize work-in-progress limits, protecting teams from overload and ensuring sustainable delivery.
  • Product-focused teams aligned with a Product Operating Model and VSM can drive accountability, continuous improvement, and deliver tangible value aligned with business objectives.

Read Full Article

like

20 Likes

source image

Hackernoon

1M

read

49

img
dot

Image Credit: Hackernoon

Agile: How to Write User Stories for Beginners

  • User stories are short descriptions of what a user wants to do in the agile project methodology.
  • A user story consists of the user, their action, and the goal.
  • User stories provide clarity, help with prioritization, and improve planning.
  • Writing acceptance criteria and avoiding common pitfalls are essential for effective user stories.

Read Full Article

like

2 Likes

source image

Medium

1M

read

149

img
dot

Image Credit: Medium

Agility and Value Delivery

  • Upstream is the initial phase of the product development cycle, where ideas are generated, hypotheses are explored, and strategic decisions are made.
  • Tools like Design Thinking, Lean Inception, and Design Sprint are integral during this phase, helping teams identify problems, test ideas, and create clear guidelines for product development.
  • A successful product development process requires a seamless connection between upstream, midstream, and downstream phases.
  • Organizations that invest in upstream enjoy a more efficient, aligned development process focused on what truly matters.

Read Full Article

like

8 Likes

source image

Scrum

1M

read

212

img
dot

Image Credit: Scrum

Agile Leadership for Startups: Evolving Growth with Flexibility and Vision

  • Agile leadership provides a valuable differentiator for startups, which often exist in high-uncertainty environments.
  • Agile leaders follow an iterative approach, test ideas through MVPs, collect real-time feedback, and adapt strategies based on insights to enable quick pivots. Slack is an example of such an organization.
  • Agile leaders break down silos and encourage cross-functional teamwork through open communication, accountability, and diversity of perspectives. This enhances decision-making and team morale.
  • Employees in startups are given autonomy to make decisions, be responsible, and act independently which frees up the organization's creativity and speed. Upskilling and trust building are also critical.
  • Agile leaders prioritize delivering value over perfection, show value even if it is halfway, time-box work into sprint intervals, frequently ship imperfect features, and collect feedback to improve more. This builds trust and momentum.
  • Agile leaders strike a balance between short-term execution and long-term vision by mapping short and long-term priorities, conducting regular retrospectives, and linking daily work to higher-level strategy.
  • Agile leaders ensure that as startups scale, they remain nimble and customer-centric by building scalable processes that view the business as growing, keeping the nimbleness culture in mind, and managing complexity with Agile frameworks like Scrum or Kanban.
  • Agile leaders lead with empathy and resilience, create a culture where mental well-being is valued, model calm in crisis, and celebrate little victories for high motivation during low periods. This fosters a healthy and long-lasting cultural environment.
  • Agile leadership provides startups with the mental disposition to swim through the tides of uncertainty, build their teams in ebbs and flows, and deliver value at every point of growth.
  • Adaptive leadership is the greatest superpower for a transforming company to shake things up within industries and through time.

Read Full Article

like

12 Likes

source image

Dev

1M

read

394

img
dot

Image Credit: Dev

Automate Your Workflows Across Jira, GitHub, and Slack

  • Learn how to automate your SCRUM workflow by integrating Jira, GitHub, and Slack to boost team productivity and streamline communication
  • Connect a SCRUM dashboard with a Slack channel to send progress alerts
  • Link GitHub commits to Jira issues for better traceability
  • By integrating Jira, GitHub, and Slack, we’ve streamlined task tracking, code management, and team communication

Read Full Article

like

23 Likes

source image

Dev

1M

read

381

img
dot

Image Credit: Dev

Start with Why: A Software Developer's Perspective

  • The 'start with why' concept, popularized by Simon Sinek, is a powerful framework for understanding and communicating the purpose of your work.
  • In software development, understanding the 'why' means grasping the underlying reason for the software's existence, the problem it aims to solve, and the impact it aims to have.
  • Benefits of understanding the 'why' include increased motivation and engagement, improved problem-solving, better communication and collaboration, and increased innovation.
  • To understand the 'why,' developers should talk to their product manager or team leader, read customer feedback, use market research, and consider the potential impact of their software.

Read Full Article

like

22 Likes

source image

Scrum-Master-Toolbox

1M

read

99

img
dot

Robert Finan: Throwing Features Over the Fence, The Disconnected PO

  • Robert Finan discusses the characteristics of a great Product Owner who fosters collaboration and ensures quick market feedback.
  • Story Mapping is a useful tool for Product Owners to focus on value and stay engaged.
  • On the other hand, a bad Product Owner remains distant and throws requirements 'over the fence,' leading to misalignment and poor outcomes.
  • Scrum Masters and Agile Coaches should address the root cause of this disconnect collaboratively.

Read Full Article

like

5 Likes

source image

Scrum

1M

read

394

img
dot

Image Credit: Scrum

The "Backlog" in Scrum: Beyond Features and Long Lists

  • The term 'backlog' in Scrum refers to a large number of things you have to deal with.
  • A backlog that is too large can hinder transparency and make it difficult to achieve a common understanding.
  • Product backlogs should not only include features, but also hypotheses, outcomes, and user problems.
  • The backlog is a tool for collaboration and should enable transparency, collaboration, and problem-solving.

Read Full Article

like

23 Likes

source image

Medium

1M

read

240

img
dot

Image Credit: Medium

From Good to Great: Shifting to Outcomes in 2025

  • The post reflects on the challenges and successes of the author's team and offers guidance for leaders navigating transformational change.
  • 2025 represents a pivotal period for the team's integration, refining its identity and positioning for sustained success.
  • The transformation that the team has undergone over the past decade was not just about technical changes but also involved redefining the culture, leadership style, and design principles of the team.
  • The post highlights the inefficiencies caused by the fragmented approach where teams were treated as projects rather than focusing on holistic value streams underpinning the product operating model.
  • The team will shift to an outcomes-first approach by measuring success by the impact that is created for customers and the business.
  • Anticipated outcomes will be documented, and teams will translate them into team-level OKRs aligning with broader organizational goals.
  • The approach will improve clarity, reduce chaos, and foster deeper engagement across teams, ensuring everyone understands the larger vision.
  • Key elements of the team's journey are discussed, including the need to create a lasting impact for the customers, business, and teams.

Read Full Article

like

14 Likes

source image

Scrum

1M

read

303

img
dot

Image Credit: Scrum

New Year's Resolution Ideas for Agile teams

  • As the new year begins, it’s the perfect time to reflect on how we can improve as Agile practitioners.
  • Here are 10 ideas for possible New Year's resolutions for your Agile team.
  • 1. Focus on Value, Not Vanity Metrics.
  • 2. Stop Adding Rules That Aren’t Scrum.
  • 3. Embrace Change, Even When It’s Inconvenient.
  • 4. Respect the Team’s Autonomy.
  • 5. Make the Sprint Goal Sacred.
  • 6. Stop Misusing Velocity.
  • 7. Say Goodbye to the Comfort Zone.
  • 8. Strengthen Relationships with Stakeholders.
  • 9. Stop Blaming Scrum for Bad Outcomes.
  • 10. Never Forget: Agile Is About People.

Read Full Article

like

18 Likes

For uninterrupted reading, download the app