| || |
Browse.develop.com is a community that was established to collect and
organize valuable web information. Our technical staff have selected and
indexed information and courses that they feel will help you stay
current on best practices across the SDLC.
53 Articles match "Products","Requirements"
| Related DevelopMentor Courses || MORE |
| | Minimal Viable Team to create a Minimally Viable Product
Despite being a bit of a mouthful to say “Minimal Viable Product” and the even more difficult to say “Minimally Marketable Feature” (also known as a “Quantum of Value” or “Business Value Increment”) are very useful concepts. What makes gives them killer power is that they speak to a secret belief held by many people (not just managers) that teams gold-plate development and create products with more than is needed. The same applies to product development: saying Yes to a feature is easy, saying No is hard, but unless you say No a lot more than Yes you won’t have a MVP. Allan Kelly's Blog - Monday, October 8, 2012
Heresy: My warped, crazy, wrong version of Agile
I increasingly feel that the way I interpret Agile, the practices and the processes, if different to the rest of the world. Perhaps this is just self doubt, perhaps because I started doing Agile-like-things before reading about XP or Scrum, perhaps this is because my version has always been more informed by Lean, perhaps this is because I have never achieved Certified Scrum anything status, perhaps because I’ve never worked for ThoughtWorks, perhaps because I hold and MBA (and thus have an over inflated opinion of myself) or perhaps I’m just wrong. And I believe it is wrong to pretend you can. Allan Kelly's Blog - Thursday, February 9, 2012
Agile: Where's the evidence?
Better requirements? Despite this one study claimed Scrum resulted in productivity improvements of as much as 600% - Benefield, “Rolling Out Agile in a Large Enterprise”. If you believe you can follow a defined process and write down a process to follow and the requirements of the thing you wish to build then waterfall is probably for you. On the other hand, if you believe the requirements, process, technology and a lot else defies definition then Agile is for you. Someone in the audience asked: “Where is the evidence that Agile works?” My response was in two parts. Allan Kelly's Blog - Friday, March 30, 2012
118 Articles match "Products","Requirements"
| The Latest from DevelopMentor || MORE |
| | Agile Clinic: Dear Allan, we have a little problem with Agile.
But, the solution is more than just changing the burn-down charts and requires a lot of time - or words - to go into. Could it be that the Product Owners are not sufficiently flexible in what they are asking for and are therefore setting the team up to fail each sprint? 'Consider this blog an Agile Clinic. On Friday an e-mail dropped into my mailbox asking if I could help. the Developers work in sprints, estimating tasks in JIRA as they go. Sprints last three weeks, including planning, development and testing. OK, sprints and estimates are good. And yo have Jira? Absolutely Right. Allan Kelly's Blog - Sunday, April 28, 2013
A Roundup of MongoDB Management Tools
Just requires the –rest command-line to mongod. Only requires that you can run Ruby or PHP on your server. The data is a great asset when optimizing applications during development and potentially invaluable when diagnosing production issues. 'I’ve been working with MongoDB for a long time now. Back in the early days, there really were no management tools analogous to RDBMS tools (e.g. SQL Server Management Studio ). Since then, things have changed significantly. The news is good. Robomongo, price: $0 / open-source, platforms: Windows, OS X, Linux. link]. link]. Michael C. Kennedy's Weblog - Monday, April 22, 2013
Requirements and Specifications
'As I was saying in my last blog, I’m preparing for a talk at Skills Matter entitled: “Business Analyst, Product Manager, Product Owner, Spy!” which I should just have entitled it “Requirements: Whose job are they anyway?” and so I’ve been giving a lot of thought to requirements. Something I didn’t mention in the last blog was that I thought: if I’m doing a talk about “need” I’d better clearly define Requirements from Specifications. There is no mention of Specifications or of Requirements. Bear with me, I’ll come back to this point at the end.) Allan Kelly's Blog - Monday, April 15, 2013
| The Best from DevelopMentor || MORE |
- Managing requirements in Agile development
I make no apologies for blogging again about Product Management because it is important and because, on the whole. So Product Management is a long run play. That is one of two reasons why Agile methods tend to underplay requirements and “Product Ownership” - because you get a lot of benefits by ignoring them to start with. The other is that Agile methods largely originated with developers who generally tend to underplay the role of requirements. In the UK confusion between Project and Product management is rampant.
Allan Kelly's Blog - Sunday, November 2, 2008
- Requirements, requirements everywhere; no clue on what to do
Twice this year I have visited companies which want to try a more Agile way of working but who have requirements coming of their ears. m talking hundreds of pages of requirements. Sometimes as big meat documents written by expensive consultants and bearing names like “Requirements Specification” or “Business Design.” Its hard to argue with such requirements documents, in part because its hard to read them and understand what they are about. One variation is a project I saw last year were the documents were not requirements documents but strategy documents.
Allan Kelly's Blog - Friday, December 4, 2009
- Minimal Viable Team to create a Minimally Viable Product
Despite being a bit of a mouthful to say “Minimal Viable Product” and the even more difficult to say “Minimally Marketable Feature” (also known as a “Quantum of Value” or “Business Value Increment”) are very useful concepts. What makes gives them killer power is that they speak to a secret belief held by many people (not just managers) that teams gold-plate development and create products with more than is needed. The same applies to product development: saying Yes to a feature is easy, saying No is hard, but unless you say No a lot more than Yes you won’t have a MVP.
Allan Kelly's Blog - Monday, October 8, 2012
- Query composition with the ASP.NET Web API
Having the ASP.NET Web API as a REST service returning data is kind of nice but to be efficient on the wire we don’t want to return more data that required only to discard it in the client. 12: public Product Get( int id). Loading the products with the original URL returns exactly the same result as before. This request “ [link] ” returns only product 11 to 15 ordered by the product name. As we have seen in a previous post just returning a collection data was real easy. As it turns out changing the service so the client can filter data is almost just as easy.
The Problem Solver - Wednesday, March 21, 2012
- Peeling Back the Onion Architecture
Writing applications that are testable requires that you separate business logic from presentation logic so that they can be independently tested. It is intended to provide some insurance against the evolution of technology that can make products obsolete not long after they are developed (the technical term is “deprecated”). For example, the ProductController class in the ASP.NET MVC application has a constructor that accepts an IProductService, which has methods to get categories and products. Download the code for this article. The Web.Ui Enjoy.
Tony and Zuzana's World - Saturday, October 8, 2011
- Software Facts - well, numbers at least
About a year ago I needed some numbers about software development - industry norms really: effectiveness, productivity, bug counts etc. It is counter productivity to invest in tools before resolving organisational and methodology issues. Productivity and quality seem to be better in object oriented languages Documentation & Bugs Producing paper documents for software development is more expensive than producing software itself Up to 400 words may be written in specification for every line of code in large systems. But he does have lots of interesting facts and numbers.
Allan Kelly's Blog - Friday, January 14, 2011
- More facts and figures from Capers Jones
Yes he acknowledges Agile, he even says it is the most productive approach in some circumstances but all his data and assumptions are cut through with the waterfall. Productivity Jones repeatedly states and shows how quality and productivity are related. The most productive teams have the lowest bug counts and shortest schedules. Jones states as little know fact “excessive staffing may slow things down rather than speed things up” Inspections (code, design, requirements) are the most efficient known ways of preventing problems. This is as good as it gets.
Allan Kelly's Blog - Wednesday, February 2, 2011