Agile Methodology News, Latest Updates and Recent Announcements on Techminis

A naukri.com initiative

New

Home

Agile Methodology News

Scrum

373

Image Credit: Scrum

Scrum is Hard and Disruptive #13 - Self-Managing Teams Rock

Self-managing teams are highly productive when they work closely with customers.
Autonomy, trust, and accountability are the foundations of self-managing teams.
Direct connection between teams and customers leads to better solutions grounded in customer insights.
Coercion doesn't work; allowing teams to self-organize results in happier employees and better business outcomes.

Read Full Article

22 Likes

Scrum

418

Image Credit: Scrum

The Cone of Uncertainty and its usage in Scrum

In traditional Project Management, cone of uncertainty was used to highlight that as we make projections about the future, specially about the cost and effort, these projections will be inaccurate early on and are likely to become more accurate as we go through the various phases of the project.
However, the challenge with the above idea was, as we complete a particular phase we would have to assume that there won’t be any further changes from that particular phase. For ex: if we completed the Requirements Gathering phase, then no further changes would be allowed from the Requirements phase.
IMHO for the software world, this is a wrong notion. If requirements are frozen without even understanding whether the end user would be using it or not, then we are not really working for the benefit of the customer.
Scrum works on the principle of Empiricism i.e. keep Inspecting and Adapting with Transparency.
In Scrum, we have Sprints and the only purpose to execute a Sprint is to get to a DONE Increment. There are no phases like requirements, analysis, architecture, code, build, test, release or others.
As the Scrum Team keeps completing work increments we can measure that work done within a Sprint and then use it to plot the cone of uncertainty.
Estimates if made only once, that too at the very beginning will be far from being accurate. Scrum Teams need to inspect and adapt continuously and keep updating their estimates regularly. Cone of Uncertainty could be a handy tool to raise transparency of estimates with everyone who is interested in them.
If you are interested to learn more about using empiricism then head to our website www.agilemania.com and make use of all the available resources.

Read Full Article

25 Likes

Scrum-Master-Toolbox

Richard Coplan: From Skeptic to Believer, Embracing SAFe for Agile Success

Richard Coplan shares his experience with implementing SAFe in a Pharma company.
Initially skeptical, Richard learned the value of SAFe, particularly in PI Planning.
Collaboration between Product Owners and Scrum teams improved through the framework.
Richard offers practical tips for using Miro and emphasizes pre-planning activities for effective work prioritization.

Read Full Article

2 Likes

Medium

Image Credit: Medium

The first Agile experience. How to become loyal to change

The author shares their experience of how they first encountered the Agile philosophy and Scrum framework, and how this led them to become a Product Owner.
The team was tasked with developing a software solution for managing retail loyalty programs.
The traditional approach to project management was replaced with Agile methodology after the founder, inspired by leading technology companies in the US that use Agile, signed a contract with ScrumTrek.
The team faced difficulties with Scrum implementation, like accommodating all stakeholders' demands and maintaining prioritization.
However, the Agile and Scrum framework allowed the team to ensure transparency, regular feedback from 'loyal' customers, and flexibility in adapting to changes in requirements and market trends.
Agile methodology helped the author's team turn their product development from solving momentary requests from the most demanding customers to a solution that would be in demand by almost all retail chains.
Their software solution became a success with 80% of the market share of retail chains in Belarus, and two nominations in the marketing tools competition as 'the best loyalty program in the CIS' and 'the best solution of the year for automating loyalty programs for retail chains.'
They conclude that adopting Agile principles and Scrum is important to ensure transparency, regular feedback, and flexibility in adapting to changes for a successful product development.
The author became an Agile Evangelist, promoting the immediate switch to Agile principles in any team or startup.

Read Full Article

5 Likes

Dev

172

Image Credit: Dev

Challenges of Code Review: How to Be Efficient and Constructive

Code review is a crucial part of the code delivery process.
It is not about nitpicking, but about addressing real issues and sharing knowledge.
Feedback should be given with empathy and a team-first mindset.
Code quality improves through continuous learning, mentorship, and collaboration.

Read Full Article

10 Likes

Medium

173

Image Credit: Medium

The Product Manager’s Balancing Act: Discovery vs. Delivery

Product discovery is the exploratory phase of product management, focusing on identifying user pain points and validating concepts.
Delivery is the execution phase, involving building, testing, and releasing the product to the market.
Balancing discovery and delivery is a challenge; involving the delivery team early in discovery and setting time limits can help.
Using data, creating feedback loops, and maintaining effective communication are key to managing both discovery and delivery.

Read Full Article

10 Likes

Scrum

200

Image Credit: Scrum

Applying Systems Thinking in Product Definition for Agile Organizations

Systems Thinking is applied in the Creating Agile Organizations (CAO) approach to define both external and internal products.
By viewing the organization as a system, the impact of every element on overall performance and agility can be understood.
Systems Thinking helps streamline product definitions for flexibility and adaptability.
The video provides practical examples and tools to implement Systems Thinking for agile product development.

Read Full Article

12 Likes

Scrum

355

Image Credit: Scrum

What Type of Scrum Master Are You?

Understanding and embracing the various dimensions of the Scrum Master role can enhance the effectiveness of your team.
The accountability of a Scrum Master is clear, but the role of the Scrum Master may differ greatly from organization to organization, team to team and person to person.
There are various types of Scrum Masters. Rotary Scrum Masters, Part-time Scrum Masters, Full-time Scrum Masters, Professional Scrum Master, Agile Coach – Scrum Master with a broader range, Scrum Master Coach, and Kanban Coach.
Rotary Scrum Master rotates among different teams, bringing fresh perspectives and cross-functional insights. Part-time Scrum Master combines the Scrum Master role with other responsibilities. Full-time Scrum Master is dedicated solely to the Scrum Master role.
Professional Scrum Master is a subject matter expert in Scrum. Agile Coach – Scrum Master with a broader range has expertise across various agile practices. Scrum Master Coach focuses on mentoring and developing other Scrum Masters.
Kanban Coach helps teams optimise their workflow, emphasising continuous delivery and efficiency. The Scrum Master's role demands a keen eye for identifying potential pitfalls before they escalate.
It requires a commitment to lean principles that eliminate non-value-adding activities and a relentless focus on understanding and meeting customer needs.
By fostering a culture that prioritises these aspects, the Scrum Master can align the team's effort with the product goal and vision, which is aligned with delivering products.
Successful Scrum Masters have strong problem-solving skills, deep theoretical knowledge and practical experience.
It is recommended to have a Scrum Master role that follows Scrum Master accountability, as described in the Scrum Guide 2020, while being aware of and not ignoring your organization's particular needs.

Read Full Article

21 Likes

Scrum-Master-Toolbox

364

Richard Coplan: The Impact of Product Owner Pressure on Agile Team Morale

Richard shares his experience working in a toxic team environment.
The Product Owner's aggressive push for deliverables demotivated the team.
Richard reflects on the importance of organizational agility in Scrum teams.
Richard recommends the book 'Shift: From Product to People' for workplace transformation.

Read Full Article

21 Likes

Medium

Image Credit: Medium

Software Management

Effective software management means everything an organization needs to ensure efficiency and optimum productivity while running its operations smoothly.
Vabro stands as a remarkable option for the management of your software — a solution that caters to all modern-day needs.
Software management involves planning processes for the acquisition, deployment, maintenance, and optimization of software applications used in organizations.
Vabro offers solid and flexible software management with configurable features, real-time monitoring, and smooth integration, allowing organizations to streamline processes and direct tools toward strategic goals.

Read Full Article

4 Likes

Scrum

Image Credit: Scrum

Agile in Medical Device: A Case Study (Part 1 of 2)

In this podcast episode, PST Jeff Lee and Patrick Campbell discuss a case study in the medical device industry.
The struggling product group faced challenges including excessive work in process, significant cost and team cuts, and lengthy compliance testing cycles.
To address these challenges, the team implemented Agile methodology.
The podcast explores the journey and results of implementing Agile in a regulated environment.

Read Full Article

Medium

241

Image Credit: Medium

The AI-First Startups: How AI-Driven Companies Are Reshaping Organizational Structures for Success

AI-first startups have new organizational structures to increase scalability and mitigate risks.
Less structured and agile models, allowing faster decision-making empower cross-functional, agile, project-based teams.
AI tools handle operational tasks, while humans focus on creativity, innovation, and relationship building.
Careem uses this agile approach integrating AI to optimize its ride-hailing operations.
AI Colleagues are set to revolutionize the enterprise software industry, capable of interacting with humans while scaling operations quickly.
An AI-first structure aims to address talent shortages by leveraging AI to handle complex processes with a few talented people.
AI systems raise concerns about data privacy and ethical use of technology, requiring strict ethical guidelines and data protection policies.
The initial investment required for AI technologies can be substantial, evaluating cost-effective AI solutions and partnerships is necessary.
Startups can harness AI's potential to enhance customer experiences and drive innovation by balancing technology with human-centric strategies.
However, startups must address the challenges accompanying this transformation - such as a legal landscape, employee disengagement, and high initial costs.

Read Full Article

14 Likes

Scrum

150

Image Credit: Scrum

Agile/Scrum Transformation Blues - Fighting the nice-to-have cave of pain with Must Have and Case Studies

Agile/Scrum transformations often face challenges despite initial promising results.
A brute force approach of mandating the transformation throughout the organization can often stall.
Applying crossing-the-chasm principles and techniques can lead to more sustainable transformations.
To create demand for transformation, focus on addressing must-have items on the organization's to-do list and utilize case studies to market its effectiveness.

Read Full Article

9 Likes

Scrum

428

Image Credit: Scrum

Scrum is Hard and Disruptive #11 - Scrum is Harder than Waterfall

In the latest episode of 'Scrum is Hard and Disruptive,' Todd and Ryan discuss why Scrum and iterative incremental development are often harder than traditional waterfall development.
Scrum intensifies the demands on engineering practices, requiring constant review, adjustment, and improvement.
Early design decisions can lead to unexpected issues, as Scrum encourages flexibility and adjustment as customer needs evolve.
Over-planning in waterfall development can lead to rushed implementations, while Scrum's shorter sprints require a shift in mindset and working style.

Read Full Article

25 Likes

Medium

Image Credit: Medium

Project Time Tracking

Vabro has developed a customized system for project time tracking that enhances project management.
Vabro's time tracking tools are specifically designed to mimic the workflow of customer projects.
Time tracking in Vabro is fully integrated with project management, providing comprehensive insights.
Vabro utilizes live collaboration, advanced analytics, and reporting for efficient project time tracking.

Read Full Article

2 Likes

For uninterrupted reading, download the app

Agile Methodology News

Discover more