Requirements Envisioning: An Agile Best Practice. 1.
When Should You Do Initial Agile Requirements Modeling? Agile Model Driven Development (AMDD), see Figure 1, explicitly includes an initial requirements envisioning effort during Iteration 0 of an agile project (what some processes might call the Warm-UP, Inception phase, or Initiation phase). Initial requirements envisioning is particularly important for scaling agile software development techniques to larger, more complex, or globally distributed development (GDD) efforts. The goal is to understand the requirements at a high-level, it isn't to create a detailed requirements specification early in the lifecycle, a traditional practice referred to as "Big Requirements Up Front" (BRUF) which proves to be very risky in practice (traditional theory is that BRUF is a best practice, but experience shows otherwise). Figure 1. 2. Some people will tell you that you don't need to do any initial requirements modeling at all. You can answer fundamental business questions. 3. 3.1 Usage Model 4.
Facebook Paper explained, plus four tips on how brands can use it. Announced late last week, it capitalises on the emerging trend that the immersive experience of content is just as important as the content itself (as also demonstrated recently by Jelly). The app has redesigned the Facebook user interface from scratch. Focusing on full-screen, bold images, the familiar "timeline" has been replaced with a Flipboardesque interface, with familiar looking mosaic-style posts appearing along the bottom.
These posts however are re-dubbed as stories; text updates become full screen black text on white background affairs, while images also receive the full screen treatment, with text overlaid and the option to scroll panoramically by tilting the phone. Albums are presented in an Instagram inspired vertical scrolling format, while videos (which, you guessed it, are full screen) play automatically. Interestingly, these feeds will be curated, and will focus on getting the most creative, most engaging content in front of users’ eyes. So what does this mean for brands? 11 Agile Myths and 2 Truths. 18inShare 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. The Role of the Analyst in Agile Projects. There is a gap in much of the literature about Agile software development practices, and on many Agile teams.
This gap is the role of Analysis in Agile projects - who does it, what is the use and value, and how does it change? The implied (and I have heard stated at least once) attitude is "we don't need no stinkin' analysts" - needless to say I feel this is WRONG! In this article I make the case that the Business Analyst can play a useful in relation to Agile teamwork - when properly aligned with the business, rather than with the development team, as is too often the case.
Why be Concerned with the Business Analyst Role? It is my contention that, without the analyst, real gaps occur. Who looks at the bigger organizational problems? Agile Development + Content Strategy: An Opportunity or Headache? Blog Post written by Gareth Morgan 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.
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. Moving from Scrum to Kanban. The invisible man. The crucial but undefined role of testers in agile. Outside-in.
Twelve (12) emerging best practice for adding user experience work to agile software development. 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. 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. Whatever facilitation technique you use to help people communicate with one another, just know that any given technique will not work forever. Behavior Driven Development. In software engineering, behavior-driven development (abbreviated BDD) is a software development process based on test-driven development (TDD). 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, with the aim of delivering "software that matters". 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. 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.
History Principles of BDD Behavioral specifications See Also Skating On The Canals & Creating Customer Memories. 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. I took it on my last day in the city. See, the ability for the citizens of Amsterdam to actually skate on their city’s canals (something that they love to do) actually happens very infrequently. The Audience Gets Ready It’s hard to capture the mood in a single picture – but for Americans reading this just think about the best tailgating experience you’ve had. Agile. Why (Most) Companies Don’t Learn. 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? While this could be true for established business in the past, it’s something that is not so clear anymore. The world is changing, and faster than ever, so (every) company has to adapt, not only once but constantly. The Agile Inception Deck « The Agile Warrior. Download Blank Inception Deck (pptx). 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. How many of your projects start off like this: You and your team get together at the start of your project thinking you are all on the same page? And when you start building something, you realize you were thinking something completely different. This happens all the time on projects: assuming there is consensus when none exists. While good teams can roll with these punches and adapt as they go, it’s a form of waste that can hurt or kill the unwary before they even get out of the gate.
Bringing User Centered Design to the Agile Environment. When the exciting opportunity to work in a post-bubble dot.com startup arose, I jumped to take it. I had the luxury of doing things exactly as I thought right, and for a while it was truly fantastic. I built a team with a dedicated user researcher; information architect; interaction and visual designers and we even made a guerilla usability lab and had regular test sessions. Unfortunately, the enthusiasm I had for my new job waned after six months when an executive was appointed Head of Product Development — who insisted he knew SCRUM1 better than anybody. Daily Stand-up Variations. A sprinkle of agile, a dash of lean. (Page 1 of 3)Whether used separately or together, agile and lean are here to stay. Now it’s just a matter of how to describe the combination of agile and lean as a business process and how to make it fit within that business, according to experts in the processes. “The best way I can describe it is if you look at how agile and lean have been used in the last decade, and in the decade from 2000 to 2010, agile has predominantly been a software development methodology and lean has predominantly been a manufacturing process,” said Alex Adamopoulos, CEO of lean and agile consultancy emergn.
“And in the next decade, which we kind of have already started, I believe they are both going to become the transformation agents in business.” Aside from defining the combination itself, organizations also have a hard time defining the best combination for the business and its projects, explained Mike Gilpin, research director at Forrester Research. OpenAgile is an open learning system for delivering value. Ten Year Agile Retrospective: How We Can Improve In The Next Ten Years. Jeff Sutherland invented Scrum in 1993 and worked with Ken Schwaber to formalize Scrum at OOPSLA'95. Together, they extended and enhanced Scrum at many software companies and helped write the Agile Manifesto. Jeff's blog reviews the origins and best practices of Scrum at June 2011. 10 ways to better lead your agile team « The Agile Warrior. The Myths and Misconceptions - The Big Agile Toolkit - Deliver agile projects to quality to time and to budget.
Table of Contents - The Big Agile Toolkit - Deliver agile projects to quality to time and to budget. Agile Software Development. Agile Use Cases in Four Steps. Het institutionaliseren van agile. Er is een anti-patroon op het gebied van agile dat me nauw aan het hart gaat. Kanban. Scrum. Methodologies.