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.

148 Articles match "Products"

  • Related DevelopMentor Courses

    148 Results found
    Showing page 1 of 8   Next >

  • 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
  • Productivity Power Tools 2012 – February 2012
    A new update to Productivity Power Tools 2012! This update includes a couple of bug fixes including a crashing bug in the Custom Document Tab Well on debug. Download now! Link: [link]. Download: ProPowerTools.vsix. Visual Studio 2012
    DevelopMentor Courses - Monday, February 25, 2013
  • Agile: Where's the evidence?
    Despite this one study claimed Scrum resulted in productivity improvements of as much as 600% - Benefield, “Rolling Out Agile in a Large Enterprise”. A few weeks ago I was presenting at the BCS SIGIST conference - another outing for my popular Objective Agility presentation. Someone in the audience asked: “Where is the evidence that Agile works?” My response was in two parts. First although it sounds like a reasonable question I’ve come to believe that this is a question that is asked by those who don’t believe in Agile, those who want to stall thing. to which the answer is certainly No.
    Allan Kelly's Blog - Friday, March 30, 2012
  • Unit testing the AngularJS code in the RAW Stack
    Again there are many ways to do so but one way I really like is Karma , another product from the AngularJS team. really nice and productive workflow. 'In the previous post we refactored the JavaScript code for our AngularJS controller a bit to make it more testable. However we didn't actually start writing any tests yet so lets create a few tests. The AngularJS controller under test Just as a quick reminder the AngularJS controller in our previous code was as follows 1: ( function () {. 6: $http.get( "/api/movies" ).then( then( function (e) {. then( function () {.
    Maurice de Bejeir - Saturday, February 22, 2014
  • An Effective Introduction to the STL Training
    I'm convinced it can improve a C++ programmer's productivity more than anything else in the language. -- Scott Meyers This seminar is a hard-core, hands-on, in-the-trenches indoctrination in the ways of the STL. Participants will gain: An understanding of the architecture behind the STL, including its core components and concepts. Mastery of the subtle differences in semantics of member and non-member functions with the same name, e.g., find, remove, etc. Knowledge of how to integrate STL containers with code expecting arrays and other C-like data structures. Exercises Further Reading
    DevelopMentor Courses - Tuesday, March 1, 2011
  • Ameba Teams and Amoeba Management
    The team may work on more than one product or project at one time - actually the concept of project should be avoided if possible. Growing takes time if it is not to undercut the teams productive capacity so needs to be done steadily over time. So if a large team looks after three similar products they might split into two teams, say 5 and 9 people each with the smaller team taking responsibility for one product while the larger team retains responsibility for the other two. tend towards using Ameba because I’m lazy. The team is responsible for its output.
    Allan Kelly's Blog - Thursday, April 24, 2014
  • #NoProjects - why projects don't make sense
    It’s a temporary group activity designed to produce a unique product, service or result. It describes the activities that meet specific objectives and can be used to introduce or improve new or existing products and services.” Destroying team destroys knowledge - knowledge has value, knowledge exists in heads not documents Project thinking induces short-termism - around quality, around productivity and around teams especially. 'In the last few months Steve Smith , myself and others have been Tweeting a lot with the hash tag #NoProjects. Until then here goes.
    Allan Kelly's Blog - Sunday, October 6, 2013
  • Guerrilla.NET (US) Training
    Debugging : Come and learn to build robust.NET applications including tools and techniques for monitoring and debugging applications in a production environment. Debugging : Come and learn to build robust.NET applications including tools and techniques for monitoring and debugging applications in a production environment. Platforms such as Ruby on Rails have shown that Model/View/Controller (MVC) is a highly productive and very testable pattern for building web applications. C# : Leverage new features of C# including asynchronous methods from C# 5.0, assuming Silverlight 5.0
    DevelopMentor Courses - Tuesday, March 1, 2011
  • Lynn Langit: About the new BISM in SQL Server 2012
    Are you using the BISM in production yet? Here’s the webcast I did (around 60 minutes) on the new BISM in SQL Server 2012 — enjoy! Here are the slides on slideshare as well. I’d love to hear how it’s … Continue reading →
    DevelopMentor Courses - Sunday, July 22, 2012
  • The good Agile demand curve
    This story is about how, using Agile software development, a team reduced the demand for software and shipped a product sooner. Not only did this make the team more productive because they had less code to maintain and bugs to fix but it also meant the business had fewer reasons to complain about bugs. And one day the “Product Owner” realised: they were not building one product but two. The Product Backlog of work to do would be better throughout of as two backlogs for two products, each with its own user/customer base. and “Can we release it yet?”
    Allan Kelly's Blog - Saturday, December 21, 2013
  • Allan Kelly: Estimating business value: adding Value poker and Dragons Den to the Agile toolkit
    good product manager or business analyst might be able to come up with some numbers. As for teams who don’t have a product manager or business analyst, well, they aren’t even going to get that far before they find questionable assumptions. One drawn from the people who are planning to build a product. This could be the entire development team, it could be just the product manager or business analyst with the product sponsor/champion. Next I ask the Entrepreneurs to pitch their product - the whole thing - to the Dragons. Do the highest value first.”
    Allan Kelly's Blog - Wednesday, December 3, 2014
  • Guerrilla.NET (UK) Training
    How can I reduce the number of bugs that make it into production? WinDBG and the plugin SOS.DLL bring a new set of tools to.NET developers that can provide insights that help you solve bugs that you see during testing but also allow you to diagnose issues occurring in production systems where the only data you can get is a crash dump file. Leverage new features of C# 4.0, including named and optional parameters and dynamic typing. Understand the new features of the core.NET runtime services including the garbage collector. Workflow 4, ASP.NET MVC and Silverlight. couldn't?
    DevelopMentor Courses - Tuesday, March 1, 2011
  • Programmers without TDD will be unemployable by 2022 (a prediction)
    And I believe, in general, software will be better (fewer bugs, more maintainable) as a result of these changes, and as a result programmer productivity will be generally higher (even if they write less code they will have fewer bugs to fix.) Exactly because of those last points: with any form of TDD in place the number of code bugs is reduced, maintainability is enhanced and productivity is increased. 'New year is traditionally the time of predictions, and several of the blogs I read have been engaging in predictions (e.g. Another blog entry I must write one day.)
    Allan Kelly's Blog - Tuesday, January 7, 2014
  • Allan Kelly: Nightmare on Agile Street
    The Product Owner. The Product Owner chuckles to himself - no over estimating on his watch! Off-shore is so so cheap…” There is a reality distortion field around the Product Owner. The Product Owner! Since when the Product Owner reports to the COO, a COO who doesn’t really have time for him and only has a shaky understanding of any IT related topic. The supplier is desperate to keep their people busy, if The Product Owner sees a programmer who’s fingers are not moving on the keyboard he turns them to stone. 'I’m awake. m lying in my bed. All good stuff.
    Allan Kelly's Blog - Monday, July 28, 2014
  • Inconvient truths of project Status reporting
    I find this suggestion very worrying because some people in the Scrum community insist that the Product Owner must be an executive (“the real product owner”) who has real power to secure the resources and changes a make the project a success. This research suggests that having a strong, senior, Product Owner could make things worse. 'Long time readers of this blog may recall that I subscribe to the high-brow MIT Sloan Management Review. They may also remember that I’m never quite sure it is worth the rather high subscription fee. Unfortunately he had the same problem.
    Allan Kelly's Blog - Wednesday, May 7, 2014
  • 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
  • Manual testing sinful?
    Unfortunately the subtly of this logic is lost on most organizations who just label everything that happens after writing actual production code “testing” and is made worse when testing is separated from the developers and, more importantly, those who understand what the system should do (the business, the BAs, the product managers, the users, etc.) 'One of the asides I made in “ Programmers without TDD will be unemployable ” which caused a bit of outrage in the testing community was my comment “Manual testing is a sin.” It is all a question of context. Manual testing is a sin.
    Allan Kelly's Blog - Sunday, February 16, 2014
  • 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
  • You are not Steve Jobs (and don't try to be him)
    Jobs was a perfectionist: products didn’t get launched unless he approved of them. Jobs would spurn products/employees who he didn’t think were up to scratch: if employees are loyal to the company and to you, and if you have a deep talent pool, and (perhaps) the stock-options are worth a lot you might get away with this. Apple products are simple because they lack so much, once launched they are refined and elaborated in the market. Thus we have the discipline of Product Management to help us. it is a copy). My concern is simply that Jobs was not a good role model.
    Allan Kelly's Blog - Friday, November 18, 2011
  • Nightmare on Agile Street 2: Managed Agile
    How can they make the Product Owners buy in? And mention of the Product Owners causes the Analyst in the other corner - the one hiding behind the ultra thin laptop - to raise an eyebrow. try a different approach: “ Instead of talking to the PMO one day, and the Product Managers the next day, and the Development Managers the day after. why don’t we go vertical and take each development team in turn, with the appropriate project, product and development managers?” Poor Product Owner, if he is lucky he’ll be shown the door, if he’s unlucky he’ll be retained.
    Allan Kelly's Blog - Tuesday, September 16, 2014
<< 1 2 3 4 5 6 7 8 >>