Mark Levison recently wrote a blog on “Scrum Alone is Not Enough”, which is the first blog of a series to uncover various Agile patterns. Till now he has published blogs on Kanban Portfolio View and Portfolio Management in the series.
What may be valuable to customers whom you do not even know in an unstructured and completely individualized market? This article suggests prioritizing your backlog using an enhanced quality model based on Maslow’s hierarchy of human needs. Search for most valuable features using the Need-Feature-Capability matrix and give those features highest priority in your backlog.
This report summarizes how the Large-Scale Scrum (LeSS) framework was used in developing a high capacity network gateway and how to grow R&D from 2 co-located teams to 20+ teams. It also describes how LeSS and agile development practices significantly accelerated the time to market and gave us the flexibility that traditional development practices never offered.
Rev. C. L. Gulati of Sant Nirankari Mission presented the opening keynote on the conference theme – Vasudhaiva Kutumbakam – The World is one family, at the Regional Scrum Gathering South Asia 2015.
The book "the nature of software development" intents to help people to organize their thoughts about value and find ways to deliver value in software development.
Dean Leffingwell’s “Leading SAFe LiveLessons” - training videos are based on Lean-Agile transformation concepts at enterprise level.
An interview with Craig Larman about LeSS and what makes it different from other scaling frameworks and using empirical process control to increase organizational agility.
With talented developers, quality advocates and user-experience designers, teams know how to deliver valuable software. But as we improve service delivery using kanban, who manages flow?
There’s no reward for being a Scrum or kanban shop if we are not delivering value to customers. We need to change our mindset, and focus on the principles that people follow and values they share.
Aleksander presents ideas on gaining greater lifecycle flexibility and improved product quality through migrating from a scrum-only platform to a visual project management solution.
Dominik Maximini researched the cultural aspects of organizations that use Scrum and published his findings, principles for implementing Scrum and suggestions on how to apply them, and a case study.
With desired agile team traits like self-organising, role blurring and skill diversification, do we still need Test Managers in agile? How are the activities which have long made up the role divested?