| |
browse.develop.com
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.
|
13 Articles match "Business Analyst","Products"
| Related DevelopMentor Courses | MORE | | 11 Agile Myths and 2 Truths Documentation is just another deliverable , if it brings you value then schedule it and product it like anything else. Agile needs more discipline from the team and what gets done should be lead from a specific role usually designated the Customer or Product Owner and usually played by a Product Manager or Business Analyst. 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. Allan Kelly's Blog - Tuesday, February 26, 2013 10 Things to make you Agile adoption successfull What ever you call the role you want someone who can: Provide advice on which practices and process to adopt, and how to best adopt them Offer examples of what they have seen work, and not work, elsewhere, and how other team tackle similar issues Observe, examine, query and challenge your thinking on what you are doing Challenge your thinking and point out opportunities and idea that you haven’t seen yet You may need to work with multiple advisors since few will be able to cover all process, practice, technology, product and strategy bases. Either way, the prognosis isn’t optimistic. Allan Kelly's Blog - Monday, May 14, 2012 Version 2 "The Rewrite" - don't do it! - never ever rewrite you system “The second is the most dangerous system a man ever designs” Fred Brooks, 1975 & 1995 Brooks was talking about software designers, architects, but I think the statement holds true not only for all software developers but for the business people who commission replacement systems. Sometimes is the business side realising that their system looks out of date - Visual Basic 6 controls on Windows Vista, or turn of the century web style. Plus, they have their own business to run - or life to live - and changing systems is only going to get in the way. ll say it again: Market led. Allan Kelly's Blog - Tuesday, August 21, 2012 |
38 Articles match "Business Analyst","Products"
| The Latest from DevelopMentor | MORE | | 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!” So now I turned to a standard textbook on requirements: Discovering Requirements: How to Specify Products and Services by Alexander and Beus-Dukis. Lets me summarise: A requirement is a thing the business wants the system to bring about A specification a restricted, more exact, statement derived from the requirement. which I should just have entitled it “Requirements: Whose job are they anyway?” nothing. Allan Kelly's Blog - Monday, April 15, 2013 Requirements whose job are they anyway? 'Later this week I’m giving a talk at Skills Matter entitled: “Business Analyst, Product Manager, Product Owner, Spy!” think there are a number of problems on this side of the business. Unfortunately Agile tends to make this problem worse because a) developers think they get to decide what is needed, b) business see Agile as a cure all. In the extreme this means developers never get to meet, talk to or understand the people and businesses that will be using the product. Undoubtedly some do but I’m far from convinced they all do. Allan Kelly's Blog - Monday, April 15, 2013 11 Agile Myths and 2 Truths Documentation is just another deliverable , if it brings you value then schedule it and product it like anything else. Agile needs more discipline from the team and what gets done should be lead from a specific role usually designated the Customer or Product Owner and usually played by a Product Manager or Business Analyst. 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. Allan Kelly's Blog - Tuesday, February 26, 2013 | -
| The Best from DevelopMentor | MORE | - Product Management an open secret, a differenciator
At the Skills Matter Agile Lean Kanban exchange the other week someone - sorry I missed you name - told me about a report from the BBC on Product Management. It turns out the report is from a branch of the BBC I didn’t know about, “BBC Academy” and it entitled “The State of Product Management 2010.” Its well worth reading if you have an interest in Product Management or the UK software development scene. Although I’ve not blogged about it for a while Product Management is one of my passions. In Silicon Valley there is a well developed role called the Product Manager. Allan Kelly's Blog - Tuesday, December 14, 2010 - Xanpan
It contains a fair chunk of what I would call “product management ideas”. On requirements Xanpan believes: There should be a dedicated requirements role staffed by a trained/experienced Product Manager or Business Analyst; both is probably overkill There should be a clear business case setting out why a team or project exists. The business case is not a shopping list of features, nor is it a large document but it should allow someone to decide the work is finished Customers are not the only stakeholders. Therefore. No model ever will be. Allan Kelly's Blog - Thursday, July 21, 2011 - 11 Agile Myths and 2 Truths
Documentation is just another deliverable , if it brings you value then schedule it and product it like anything else. Agile needs more discipline from the team and what gets done should be lead from a specific role usually designated the Customer or Product Owner and usually played by a Product Manager or Business Analyst. 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. Allan Kelly's Blog - Tuesday, February 26, 2013 - IT: Better to be effective or aligned?
Like the Rettig piece they are concerned with internal IT projects rather than products for sale (my main area of interest and experience.) From this survey they are able to divide companies into four categories - a nice 2x2 matrix based on whether a company has effective (or ineffective) IT and whether the IT is aligned with business strategy (or pursuing its own.) These four categories are: IT Enabled Growth : These companies have highly effective IT groups who are closely aligned to the business. This occurs when IT operations are aligned to the business (i.e. Allan Kelly's Blog - Saturday, December 1, 2007 - Version 2 "The Rewrite" - don't do it! - never ever rewrite you system
“The second is the most dangerous system a man ever designs” Fred Brooks, 1975 & 1995 Brooks was talking about software designers, architects, but I think the statement holds true not only for all software developers but for the business people who commission replacement systems. Sometimes is the business side realising that their system looks out of date - Visual Basic 6 controls on Windows Vista, or turn of the century web style. Plus, they have their own business to run - or life to live - and changing systems is only going to get in the way. ll say it again: Market led. Allan Kelly's Blog - Tuesday, August 21, 2012 - 10 Things to make you Agile adoption successfull
What ever you call the role you want someone who can: Provide advice on which practices and process to adopt, and how to best adopt them Offer examples of what they have seen work, and not work, elsewhere, and how other team tackle similar issues Observe, examine, query and challenge your thinking on what you are doing Challenge your thinking and point out opportunities and idea that you haven’t seen yet You may need to work with multiple advisors since few will be able to cover all process, practice, technology, product and strategy bases. Either way, the prognosis isn’t optimistic. Allan Kelly's Blog - Monday, May 14, 2012 - Why try Kanbnan?
The easy way to spot this is the absence of someone with a title like: Product Owner, Business Analyst, Product Manager or similar. Nor is there a lot of point to running a product backlog if items are being delivered rapidly or not done. In my last post “ Scrum doesn’t work for us; should we try Kanban? I gave a warning about adopting Kanban because Scrum doesn’t seem to work. Having given advise on when not to use Kanban I feel I need to suggest when choosing Kanban is the right decision. Here goes…. you can’t force a customer to respond). Allan Kelly's Blog - Sunday, October 21, 2012 %>
| |   |
