menu
techminis

A naukri.com initiative

google-web-stories
Home

>

Agile Methodology News

Agile Methodology News

source image

Scrum

1M

read

266

img
dot

Image Credit: Scrum

Increase Your Impact As An Agile Practitioner!

  • As Agile Coaches (and Scrum Masters), it’s your job to surface impediments blocking flow and team effectiveness, even if that leads to uncomfortable or different-than-usual conversations.
  • One strategy is to use your intuition, but it can be fraught with biases and wrong heuristics.
  • The preferred approach is to use data, evidence-based feedback, and insights from scientific research to improve team and organizational effectiveness.
  • Agile practitioners should focus on collecting team data, gathering multi-team data, analyzing qualitative data, and using scientific insights to drive improvement actions.

Read Full Article

like

16 Likes

source image

Alvinashcraft

1M

read

108

img
dot

Dew Drop – October 1, 2024 (#4276)

  • Uno Platform Team shares how can we bridge the gap between Model-View-Update (MVU) architecture and Model View ViewModel (MVVM), using a sample app built using the bridge pattern.
  • In this post, Vinoth Kumar Sundara Moorthy shares the .NET product team's perspective on what’s new in .NET 9 and explains the latest updates and features.
  • Lee Stott introduces Microsoft Learning Hubs, which are designed to help users learn new skills and earn certifications, discuss the different learning paths, and highlight the features and benefits of using these hubs.
  • Dev Proxy is a simple and lightweight local development proxy that provides simulating authentication and authorization capabilities. In this article, Waldek Mastykarz and Garry Trinder introduce the new version of Dev Proxy v0.21 and explains how you can use it.
  • Kaushik Kislay announces the General Availability (GA) of Native Authentication for Microsoft Entra External ID, which offers an easy way to enable authentication via external identity providers, such as Microsoft Account, Google Sign-In, and Facebook Login.
  • Harshada Hole introduces the concept of Instrumentation Profiling and explains how to use the Persistent Target Selection capability of the dotMemory Memory Profiler to effortless Instrumentation Profiling.
  • Andrea Chiarelli explains the Bearer scheme, which is a token-based authentication scheme that allows HTTP requests to authenticate using a token passed in the Authorization header of the request.
  • Ali Hamza Ansari shares some tips for boosting code readability and manageability in ASP.NET Core by leveraging built-in features and third-party tools.
  • Geoff Graham explains the differences between CSS Masonry and CSS Grid and provides examples to show when to use each layout technique.
  • Jeremy D. Miller explains how to scale event projections and subscriptions using the Critter Stack, which is a set of open-source libraries that provide a complete Event Sourcing and CQRS framework for .NET.

Read Full Article

like

6 Likes

source image

Medium

1M

read

63

img
dot

Image Credit: Medium

Building the Perfect Scrum Team: The Product Manager’s Role

  • The product manager plays a crucial role in ensuring the success of a Scrum team.
  • They need to balance their duties while working with developers, designers, and stakeholders.
  • The product manager promotes transparency, collaboration, and aligns the team with the product's goals.
  • Regular communication with stakeholders and tracking team performance ensures the delivery of value.

Read Full Article

like

3 Likes

source image

Scrum

1M

read

420

img
dot

Image Credit: Scrum

The Kanban Practice That Equips Teams For Self-Management

  • The Kanban Method is a management method made up of principles and practices to be applied to whatever process is in place (which could be Scrum).
  • One of the practices is to make policies explicit.
  • Explicit policies can be used to define the boundaries within which teams can work and the level of empowerment they have.
  • Team members look to the policies instead of referring to a manager, while managers begin to trust teams to self-manage because they trust the system as described by the policies.
  • Having explicit policies in place lays the foundation for improvement.
  • The Kanban Method only guides teams and organisations to make policies explicit, but it does not prescribe what they should be. It’s up to the team and the organisation to define and evolve their policies in their context.
  • Scrum already comes with some policies that are already made explicit.
  • Policies should remain dynamic as circumstances change.
  • Making policies explicit is a simple but powerful practice, but some teams struggle to get started.
  • By exploring this practice teams and organisations can equip their teams for greater levels of self-management.

Read Full Article

like

25 Likes

source image

Scrum

1M

read

13

img
dot

Image Credit: Scrum

Defining Work As Problems To Solve

  • Product development is complex and organizations often struggle with predictive decision-making in unpredictable environments.
  • Beliefs about customer needs are often untested assumptions that may later prove to be incorrect.
  • To avoid wasted effort and remain competitive, organizations can connect their product teams with customers and engage in customer discovery and learning practices.
  • TheScrumMaster.co.uk offers eLearning courses on Scrum & Agile to help individuals learn and gain certification in these methodologies.

Read Full Article

like

Like

source image

Scrum

1M

read

330

img
dot

Image Credit: Scrum

What Is a Usable Increment?

  • A usable Increment in Scrum revolves around providing immediate value and a platform for feedback and continuous improvement.
  • A usable Increment must meet the predetermined 'Definition of Done' (DoD) and be fully functional and ready to be used.
  • The Increment should provide value to the customer and be fully integrated with the existing product.
  • A usable Increment is potentially releasable, gathers feedback, and ensures sustainable development pace.

Read Full Article

like

19 Likes

source image

Scrum-Master-Toolbox

1M

read

298

img
dot

Eli Goodman: How A/B Testing Can Derail Product Development, A Product Leadership Story

  • Eli Goodman, Head of Product at Tuple, discusses the drawbacks of over-reliance on A/B testing in product development.
  • A/B testing, when misused, can slow down product progress and lead to a bloated team structure.
  • Eli shares strategies on how to avoid this trap and take responsibility for product decisions.
  • Product teams should avoid hiding behind A/B testing and move forward with confidence.

Read Full Article

like

17 Likes

source image

Scrum

1M

read

371

img
dot

Image Credit: Scrum

Tackling Projects in a Product Operating Model World - Aka Herding Wildcats Down Waterfalls

  • Projects and initiatives often take a backseat in a Product Operating Model world.
  • While individual products operate in an agile manner, the integration across products tends to follow a waterfall approach.
  • To handle cross-product initiatives, it is important to prioritize effectively, maintain transparency, and facilitate collaboration.
  • The focus should be on outcomes, continuous adjustment based on evidence, and optimizing for the whole.

Read Full Article

like

22 Likes

source image

Medium

1M

read

267

img
dot

Image Credit: Medium

Shape → Bet → Build. A New Way to Build Digital Products

  • Shape Up is a refreshing read that addresses common challenges in building and shipping software.
  • The shaping process involves addressing risks, identifying pitfalls, and writing a pitch for the potential bet.
  • Betting replaces backlogs, with stakeholders reviewing well-shaped pitches in a betting table meeting.
  • The building phase focuses on assigning projects, starting with a core component, dividing the project into territories, and prioritizing what matters.

Read Full Article

like

16 Likes

source image

Scrum-Master-Toolbox

1M

read

153

img
dot

Eli Goodman: The Risk of Investing in Non-Critical Features That Remove Focus From the Core Experience, A Product Leadership Story

  • Eli Goodman, Head of Product at Tuple, shares a failure story about investing in non-critical features that distract from the core user experience.
  • He reflects on a project to build a community feature that didn't take off, leading to the realization of the importance of focusing on features that are critical to the core user path.
  • The episode discusses how to identify which features truly belong in a product and when it's time to abandon an idea.
  • Eli Goodman has 17 years of experience in software teams, transitioning from engineering to product management and currently serving as the Head of Product at Tuple.

Read Full Article

like

9 Likes

source image

Scrum

1M

read

403

img
dot

Image Credit: Scrum

Understanding Product Pricing Models: Choosing the Right Pricing for Your Product

  • Product pricing is a critical decision for any business.
  • Cost-plus pricing is the simplest pricing strategy.
  • Value-based pricing relies on the product's perceived value from the customer's perspective.
  • Penetration pricing aims to capture market share by offering low initial prices.
  • Skimming pricing sets high initial prices and gradually lowers it over time.
  • Freemium pricing offers basic features for free and additional features for a fee.
  • Subscription pricing charges customers a recurring fee in exchange for access to a product or service.
  • Pay-per-use pricing charges customers based on how much they use the product.
  • Bundle pricing involves offering multiple products or services at a discounted price.
  • Dynamic Pricing adjusts the price of a product in real-time based on market demand and competition.
  • Geographic pricing varies the price of a product based on where the buyer is located.

Read Full Article

like

24 Likes

source image

Scrum

1M

read

0

img
dot

Image Credit: Scrum

What is Scrum? Scrum is an IDEA

  • Scrum is an idea that originates from the game of Rugby, where a team works together towards a common goal.
  • The principles of Scrum emphasize self-organizing teams, fast feedback loops, and frequent delivery of high-quality code.
  • Scrum is based on a set of agreements that a team adopts to focus, communicate openly, and work together towards long-term goals.
  • Scrum involves repeated cycles of planning, release, and retrospective, enabling stakeholders to understand the progress of the product.

Read Full Article

like

Like

source image

Medium

1M

read

362

img
dot

Image Credit: Medium

The Power of Using OKRs: Mastering the Chess Game of Software Services

  • KPIs can lead teams to focus solely on outputs, neglecting strategic outcomes.
  • Organizations face challenges when relying solely on KPIs.
  • OKRs consist of strategic gambit, building a strong foundation, maximizing resources, and monitoring progress.
  • Embracing OKRs empowers organizations to navigate challenges and succeed in software services.

Read Full Article

like

21 Likes

source image

Scrum-Master-Toolbox

1M

read

204

img
dot

BONUS: Mastering Product Management in a Remote World, Insights from Tuple’s Head of Product, Eli Goodman

  • Tuple, a remote pair programming service, has unique features that sets it apart from generic screen-sharing tools. Tuple is designed to stay “one inch wide, one mile deep” to ensure the tool stays focused on enhancing the pairing experience without getting in the way.
  • Managing a distributed team across the U.S. and Europe comes with its challenges, Eli highlights the importance of alignment and ensuring everyone is on the same page, despite working remotely.
  • Effective communication is the backbone of remote work, and Eli shares some of the practices that have helped Tuple’s team stay aligned and collaborative. Tuple has created a remote work environment where conversations are naturally sparked, and collaboration is effortless.
  • At Tuple, engineers only have three meetings a week, leaving the rest of the time open for pairing and creative work. One of the key insights Eli shares is how Tuple has evolved its remote pairing process.
  • While pairing is typically associated with programming, Tuple uses pairing for other activities, like design or planning sessions. This practice fosters a culture where team members collaborate on various tasks that benefit from shared perspectives and live problem-solving.
  • Tuple’s ideal customers are teams that value deep collaboration through pair programming. The platform’s most important offering is the ability to make remote pairing seamless and intuitive, something traditional tools fail to deliver.
  • Looking ahead, Eli shares Tuple’s plans to continue investing in quality and lowering the barriers to remote pairing. One exciting potential direction includes creating a “social layer” within the app to help users feel more connected with their teammates.
  • Another idea is incorporating non-human pairing agents that could assist with specific tasks. Eli recommends The Mom Test by Rob Fitzpatrick, a must-read for anyone working in product management.
  • The book teaches how to talk to customers in a way that gets honest, useful feedback rather than polite responses that don’t help improve the product.
  • Eli Goodman has been working on software teams for 17 years. He’s now the Head of Product at Tuple, a remote pair programming service used by companies such as Figma, Shopify, and many others in the software industry.

Read Full Article

like

12 Likes

source image

Medium

1M

read

140

img
dot

Image Credit: Medium

Sprint Planning and Execution: Keeping Your Team on Track

  • Effective sprint planning is crucial for alignment, efficiency, predictability, and motivation.
  • Prepare for sprint by reviewing and refining the product backlog and setting a sprint goal.
  • Have entire Scrum team attend sprint planning meetings to involve everyone's perspective.
  • Discuss and estimate effort, dependencies, and concerns on each backlog item.
  • Break down user stories into detailed tasks and set realistic estimates.
  • Monitor progress, address blockers, and use sprint review and retrospective meetings to reflect and adjust.
  • Foster open communication, avoid scope creep, celebrate successes, and use tools wisely.
  • Common pitfalls include overcommitment, ignoring team feedback, and lack of clear goals.
  • Experiment and find what best suits your team's dynamics.
  • Follow for daily insights on product management.

Read Full Article

like

8 Likes

For uninterrupted reading, download the app