BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Scrum Content on InfoQ

  • Reactions to the First Certified Scrum Developer Course

    Dave Nicolette shared his candid feedback about the first official Certified Scrum Developer course, presented on the Lean Dog boat (Cleveland, Ohio) last week by Ron Jeffries and Chet Hendrickson. Though, he mentioned the learnings and advantages of attending the course but his thoughts did manage to re-ignite the debate about the significance of CSD.

  • The Emerging Dynamics of Certification

    Scrum and agile certification is now very much in focus. The 'certification story' is unfolding to become a major subject of debate in 2010. The story has several facets, with action from the Scrum Alliance, Scrum.org and the community-at-large, including notable bloggers and the Agile Skills Project. At issue is the basic value of certification.

  • Is the 'C' Word Dividing the Agile Community?

    There has been a lot that has been said about Scrum Certifications. Some people like the idea and others oppose it vehemently. Ron Jeffries recently stated that though he has been writing about the good aspects of Scrum Alliance’s Certifications but he is concerned that the 'C' word is keeping away a lot of valuable members of the Agile community.

  • Agile in the Mainstream

    Mainstream Agile is an idea whose time appears to have arrived. Larger consulting services firms are now touting "agility", with firms like IBM Global Business Services and Cap Gemini pitching Agile-related service offerings. Given this kind of sudden mainstream popularity, what does it mean for Agile in general? What does "mainstream" Agile look like? What's in mainstream Agile?

  • Scrum Gathering: Community of Practice

    The Agile community is developing consensus around three important areas of practice: requirements gathering, agile coaching, and open space formats for group learning. At the recent Scrum Gathering, these topics were prominent topics of discussion on Day 1, Day 2, and Day 3 of the event. InfoQ explored each of these further to gain a better understanding of their place in Agile.

  • 2010 US Scrum Gathering, The After-Shocks

    The 2010 US Scrum Gathering went down 2 weeks ago in Orlando, and InfoQ has followed the buzz since. Enjoy what we've found from the vast pool of great blogs, articles, notes, videos, pictures, presentations and more that have surfaced since the event.

  • Most Effective Team Structure

    Agile talks about small team sizes with the magic numbers of 7 plus minus 2. Agile also recommends whole teams. Whole team is a concept that advises for having sufficient skills within the team itself to get the job done. Thus the development team has the testing skills, database skills, user interface skills, apart from the core development skills. Is defining the team structure this easy?

  • US Scrum Gathering 2010 Kicks Off With a Day of "Deep Dives"

    The 2010 US Scrum Gathering kicked off Monday in Orlando with a buzzworthy day of "deep dive" learning, collaboration, and healthy debate.

  • Uncovering Serious Flaws of Agile and Scrum

    Software development is known to be a creative process. The failure of traditional methods, where the dynamic environment of software development was ignored, made Agile methods fairly popular. There has been a growing adoption of Agile methodologies, particularly Scrum. However, is everything all right with Agile? Kai Gilb does not think so. He suggested that there are serious flaws with Agile.

  • Scrum/Agile Failings or the Theses of Uncle Bob Martin

    In response to a question about the Inherit Shortcomings of Scrum/Agile - Uncle Bob Martin penned (in the spirit of Martin Luther), 7 theses: No Technical Practices, 30 Day Sprints are too long, Scrum Master sometimes turns into Project Manager, Scrum carries an anti-management undercurrent, and others.

  • Is Scrum Certification Having Another Makeover?

    Scrum Certification is one debate that refuses to die down. First, it was about the hollow nature of certification for which there was a comment “Pay the tuition, sit through a couple days of class, and you're in”. Subsequently a new format was devised, which too failed to enthuse the Agilists who were against this certification philosophy. Is there another makeover on the anvil?

  • Minibook: Scrum and Kanban: Making the Most of Both

    Scrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. So how do they relate to each other? The new InfoQ minibook by Henrik Kniberg and Mattias Skarin, Kanban and Scrum - making the most of both, clears up the fog so you can figure out how Kanban and Scrum might be useful in your environment.

  • Individual Rewards on a Scrum Team

    In a recent LinkedIn discussion the question was asked "Should we have an individual recognition reward on a Scrum team". This prompted some intense debate with points both for and against.

  • ScrumBan - Evolution or Oxymoron?

    Kanban workshops, courses and conferences are springing up, and practicing Agilists are investigating what this method, adapted from Lean, offers their teams. Attractive benefits are cited, from revealing bottlenecks to happy teams experiencing more "flow". But thought leaders warn that Kanban's laid back approach is "kryptonite" to Scrum's call to resolve impediments immediately.

  • XP or Scrum, Either, Both, or Neither?

    Which is better? Scrum or XP? Is there one that is more applicable than the other or is there another alternative?

BT