Agile
Hier verzamel ik alle relevante websites rond Agile ontwikkelingsmethodieken met specifieke aandacht voor Scrum en Smart. Mar 3
Get flash to fully experience Pearltrees
10 in Share I deliver a lot of Agile training courses and I give a lot of talks about Agile ( BCS Bristol tonight ). There are some questions that come up again and again which are the result of myths people have come to believe about Agile. Consequently I spend my time debunking these myths again and again.
11 Agile Myths and 2 Truths
Posted by Shane Hastie on Dec 05, 2008 Sections Process & Practices , Architecture & Design
The Role of the Analyst in Agile Projects
Over the past 12 months, Critical Mass has integrated agile development practices into some of our client engagements. Instead of doing most of the content strategy and execution ourselves, we collaborate with the client to discover and build something together. Is agile an opportunity or a headache for the client-agency relationship? Yes and yes. Like any new way of getting work done, there are benefits and drawbacks to consider.
Agile Development + Content Strategy: An Opportunity or Headache?
Kanban
Top 100 Agile Books (Edition 2012)
It took me four hours, three coffees, two toilet breaks, and one unpredictable wi-fi connection, but here it is… the annual Top 100 Agile Books 2012 , based on ratings from Amazon and GoodReads . There are some amazing changes at the top of the list this year. Most notable is the new entry at #1 of The Lean Startup , by Eric Ries. Clearly deserved, as the whole Agile community has been talking about it all year. But that’s not all. Specification by Example , by Gojko Adzic, makes a spectacular jump to the 2nd slot in the list.
Handling Bugs in an Agile Context | Test Obsessed
I was honored to be included on the lunch and learn panel at the Software Quality Association of Denver (SQuAD) conference this week. One of the questions that came up had to do with triaging bugs in an Agile context. Here’s my answer, in a bit more detail than I could give at the panel.This article first appeared in issue 224 of .net magazine – the world's best-selling magazine for web designers and developers. Until recent years, the traditionally accepted process for software and web development has been the Waterfall methodology. Increasingly however, Agile software development methodologies have gained traction – including, among others, Scrum, Extreme programming (XP), Lean software development and Feature-driven development. But what exactly are they? Where did they come from?
The new design methodologies
Scrum
10 ways to encourage customer reviews online
Customer reviews are a hugely important in ecommerce for improving your conversion rate, and can lead to an uplift of 18% in sales. Research has shown that 61% of customers read online reviews before making a purchase decision and 63% of customers are more likely to make a purchase from a site that has user reviews. Annoyingly though, customers generally can’t be bothered to leave their feedback.
Rachel Davies - Moving from Scrum to Kanban from NDCOslo on Vimeo . Many teams who are already using Scrum would like to know what benefits they can get by moving to Kanban. Dropping the Sprint timebox can seem quite scary but on the other hand spending less time planning and estimating seems attractive to many developers. How do you know that you haven't thrown the baby out with the bathwater?
Moving from Scrum to Kanban
Outside-in
User Story
How experienced UX practitioners have adapted to work happily in Agile environments Agile development originated from a place where user experience practice was weak In my last blog essay I explain how I see that the type of product we build has big effect on the process we follow to build it. In the lower left of my simple 4 quadrant model I place software built internally for use by an organization where usage is mandatory for its target users. I explained that this is where Agile processes originated from. I also explained that strong user experience practice rarely exists here.
Twelve (12) emerging best practice for adding user experience work to agile software development
Most things work…until they don’t
I have a secret to tell you when it comes to facilitating agile teams. I’ll whisper it to you… Most things work, until they don’t. Yep, that’s it. That’s the secret.
Behavior Driven Development
In software engineering , behavior-driven development (abbreviated BDD ) is a software development process based on test-driven development (TDD) . [ 1 ] [ 2 ] Behavior-driven development combines the general techniques and principles of TDD with ideas from domain-driven design and object-oriented analysis and design to provide software developers and business analysts with shared tools and a shared process to collaborate on software development. [ 1 ] [ 3 ] Although BDD is principally an idea about how software development should be managed by both business interests and technical insight, the practice of BDD does assume the use of specialized software tools to support the development process. [ 2 ] Although these tools are often developed specifically for use in BDD projects, they can be seen as specialized forms of the tooling that supports test-driven development. The tools serve to add automation to the ubiquitous language that is a central theme of BDD. [ edit ] HistoryIntroducing BDD « DanNorth.net
History: This article first appeared in Better Software magazine in March 2006. It has been translated into Japanese by Yukei Wachi , Korean by HongJoo Lee , Italian by Arialdo Martini and French by Philippe Poumaroux . I had a problem. While using and teaching agile practices like test-driven development (TDD) on projects in different environments, I kept coming across the same confusion and misunderstandings. Programmers wanted to know where to start, what to test and what not to test, how much to test in one go, what to call their tests, and how to understand why a test fails.I’m just back from a whirlwind trip to Amsterdam where I was honored to be invited to speak at Hippo’s Client Day as one of the key speakers. My talk was on how context is such an important part of the content marketing process. But two things happened during my trip (well I also fell of a loaned bicycle and bruised a rib but that’s another story for different beverages) that I found particularly interesting as it relates to us as marketers and storytellers. So, the picture above is apparently a rare treat.
Skating On The Canals & Creating Customer Memories | The Mythic Marketer
Agile
Why (Most) Companies Don’t Learn | Agile Software Development
I’ve been thinking about and researching the topic of organisational learning for some time now. Last year, I presented on the topic at LESS 2011 , but realized it was time to take some time and write about it. So this is the first post of a series to explore the topic, which I’m also hoping will help me clarify my view on the subject. Organisational learning. Should anyone care ? My hope is that this goes without saying, but I guess that the first question to be asked is why should anyone care about learning?One area most agile methods are completely silent on is project chartering. Below is a lightweight you can use to fill this gap and get your project headed in the right direction long before the first line of code every gets written. 10 questions to ask at the start of your next project It starts out so hopefully. As you begin the project, you and your team are all on the same page. Or so it seems.
The Agile Inception Deck « The Agile Warrior
Kanban
Scrum
Methodologies