InfoQ Homepage Scrum Content on InfoQ
-
/articles/agile-goal-setting-appelo/en/smallimage/soccer-goal.jpg)
Agile Goal Setting
It is well understood that too succeed in developing great applications or even great things in our lives we need goals. Goals that motivate and push us to go beyond the ordinary. However if we Google Agile Goal Setting there are few items that give much consideration to what these should look like or how to create them. Jurgen Appelo looks at what it takes to make great goals.
-
/articles/technical-debt-levison/en/smallimage/technicaldebt.jpg)
Technical Debt a Perspective for Managers
Developers often talk about Technical Debt saying its slowing your projects down. What are they really saying? What measures can you take to reduce it before it cripples your projects?
-
/articles/agile-employer-job-search/en/smallimage/smallimage.JPG)
Finding an Agile Employer
The rocky job market of the last couple years has left many people looking for work. Agile software development is appealing to many job seekers, but not all jobs are alike. If you want a job in Agile software development, using a framework like Scrum, you need a plan of action that spans all three phases of your job search: reseach/preparation, interviewing, and assessing your opportunities.
-
/articles/product-backlog/en/smallimage/booksmall.jpg)
Working with the Product Backlog
Roman Pichler discusses the product backlog along with techniques for effectively grooming it. Complicated applications of the product backlog are covered as well as how to handle nonfunctional requirements and how to scale a product backlog for large projects. This is a chapter excerpt from Roman's book: Agile Product Management with Scrum.
-
/articles/scrum-management-deemer/en/smallimage/scrum.jpg)
Manager 2.0: The Role of the Manager in Scrum
Scrum defines just three roles, Product Owner, Scrum Master, and Team - not Manager. Pete Deemer explores the consequences for Managers, how the managerial role might be redefined (including a sample job description), and appointing the manager as Scrum Master.
-
/articles/limits-of-agile/en/smallimage/image_agile_border.jpg)
The Limits of Agile
The problems faced by teams that are attempting Agile in non-traditional settings aren't that Agile principles are inapplicable, nor that the feedback cycle is doomed to failure; but rather, outside of a certain Agile sweet-spot there are additional barriers and costs to applying Agile techniques. None of these obstacles prevents Agile in itself but each increases the cost of getting to Agile.
-
/articles/multitasking-problems/en/smallimage/JugglingBalls - small.jpg)
Multitasking Gets You There Later
It's now well understood that multi-tasking on a personal level is bad and slows down the rate at which we work. One of the key challenges of new Agile/Scrum teams is the number of projects that they have on the go. Agile teaches us that a team should work on one project at a time or it will thrash. Roger Brown shows in depth why this happens.
-
/articles/adkins-coaching-agile-teams-chapter2/en/smallimage/cover.jpg)
Book Excerpt: Coaching Agile Teams by Lyssa Adkins
Very little in our education or experience properly prepares a ScrumMaster or project manager for the role of agile coach. This leaves most wondering, "What is my role in a self-organized team? How do I help the team yet stay hands-off?" This chapter, excerpted from the book Coaching Agile Teams, shows you how to activate the journey toward high performance in both provocative and practical ways.
-
/articles/cohn-chapter8/en/smallimage/cover.jpg)
Book Excerpt: Succeeding with Agile: Software Development Using Scrum
This is a book excerpt from Mike Cohn's new book "Succeeding with Agile: Software Development Using Scrum". This article describes the primary adjustments individuals must make as they transition from traditional roles to Scrum. The focus is on how these roles change, rather than on a thorough description of each role.
-
/articles/agile-teamwork/en/smallimage/team_building_ring.jpg)
Agile Teamwork: The Leadership - Self-management Dilemma
Self-managed teams are unstable and are successful when the ‘Leadership – Self-Management’ dilemma is understood and dealt with. Too much central control destroys agility, inhibits creativity and resists change. Too much self-management leads to chaos and anarchy and destroys a team. A successful Agile Team operates as far along self-management as it can, without tipping over into chaos.
-
/articles/scrum-and-strategy/en/smallimage/scrum.jpg)
Scrum And Strategy
If Scrum is all about short term, how then do the strategy folks work in such an ecosystem? More importantly, how does it help business leaders make and live up to important commitments? Good questions, but there aren’t easy enough answers. Doesn’t all this make strategy and Scrum look like the two poles of a magnet, or even further – the two extremes of the planet?
-
/articles/product-management-in-agile/en/smallimage/images_cartoon_charatcer.jpg)
How Product Management Must Change to Enable the Agile Enterprise
When development teams adopt agile, product management is often caught off guard by the amount of work added to their already overflowing plate. Agile calls for new skills, and traditional staffing models do not typically accommodate the new product owner role. Given that most product managers are overworked, how can they manage these new activities to derive more value?