Category: collaboration

  • Daily Collaboration: Bridging Business and Development

    Daily Collaboration: Bridging Business and Development

    The fourth principle of the Agile Manifesto emphasizes the necessity of daily collaboration between business people and developers throughout a project. This approach fosters better understanding, reduces misunderstandings, and enhances trust, ultimately leading to products that meet customer needs. Such partnerships enable continuous improvement and innovation, avoiding the pitfalls of isolated workflows.

  • Scrum Bubbles Recommendation of the Week

    Have you checked out the Agile Uprising Coalition yet? If you haven’t, you should. According to their website, they are a “purpose-built network that focuses on the advancement of the agile mindset and global professional networking between and among practicing agilists.” I check out Agile Uprising regularly to see what my fellow agilists say about…

  • Hackathon How-To

    Hackathon How-To

    Recently, my company did its second-ever hackathon. It was somewhat thrown together, but I think the results were amazing. It provided all the scrum teams with a much-needed break from the everyday grind, but more importantly, it gave them the opportunity  to work on something they felt passionately about. My company wants to give these…

  • What is it like being married to an agile coach, anyway?

    On 03/11/14 7:31 AM, Robert Neil wrote: ——————–  Do you do private agile training? I think being agile is very important when participating in projects that require difficult positions.I would like you to show me how to properly scrum my wife. As a coach would you actually assist, or just give verbal advice during the “meeting”?…

  • Some Thoughts on Scope Creep

    According to wikipedia (and various other sources), scope creep is defined as follows: Scope creep (also called requirement creep and feature creep) in project management refers to uncontrolled changes or continuous growth in a project’s scope. This can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered harmful.   In an agile project, however, sometimes uncontrolled…

  • How many types of Agile Retrospectives are there, anyway?

    The other day I noticed that we were getting pretty stagnant with our sprint retrospectives.  I have been asking these questions: “What went well? What went less well? What areas improved from last sprint? What areas need improvement?”  Sometimes we get some good discussions going, but most of the time I have to prod my…