Skip to main content

juha riissanen's Library tagged no_tag →  View Popular

Overview of Extreme Programming (XP) : Learn Software Development

  • Extreme Programming (XP) is a software engineering methodology which is intended
    to improve software quality and responsiveness to changing customer
    requirements. As a type of agile software development, it advocates frequent
    “releases” in short development cycles (timeboxing), which is intended to
    improve productivity and introduce checkpoints where new customer requirements
    can be adopted.
01 Oct 09

Three Interests causing alienation and a leadership vacuum by @aritikka

  • Small batches fully done


    This is The Way to reduce complexity, to enable measurability,
    control and agility     to the organization. This is a Lean revolution,
    dramatic change owned, driven and personally needed by the top management.

  • Please differentiate between competence and roles!

  • 3 more annotations...
22 Sep 09

Glen Alleman's note on Agile to learn about System Engineering

    • Quote of the Day





      • Science determines what IS…
      • Component engineering determines what CAN BE…
      • Systems engineering determines what SHOULD BE.

      Systems Engineering is a holistic, product oriented engineering discipline
      whose responsibility is to create and execute an interdisciplinary process to
      ensure that customer and stakeholder needs are satisfied in a high quality,
      trustworthy, cost efficient and schedule compliant manner throughout a system’s
      life cycle.


      Much of the agile world can learn from how Systems Engineering is applied to
      software intensive products in domains outside the internal IT development
      shop.

What’s So Great About Flow by @Jeantabaka

  • Lean principle of Flow. Productivity is not about filling our plates to maximum
    capacity during planning meetings. Rather, we encourage team members to build in
    “slack” in their commitments.
  • They seek Flow of value delivery versus 100% allocation. That is: “Of our total
    time at work in this 2 weeks, we really only have this much time available
    (e.g.  X hours). And because we need to allow room for discovering what we
    can’t know, we are only going to sign up for and commit to this much (e.g. 80%
    of X) work.” As for “done”, a team commits to a certain, attainable level of
    doneness that includes more than code: testing, documentation, code review,
    acceptance, etc.
  • 2 more annotations...

Allan Kelly on The Quick & Dirty Myth

  • All my experience tells me that when someone chooses a “quick and dirty” path a)
    it takes far longer than is expected, b) the quality is so low we go around the
    loop a few times making things slower, c) every one involved will feel bad, even
    “dirty” about the soltiion and d) it causes more problems very soon.
  • My solution: don’t accept this framing of the problem. Get more options on the
    table. (If you can stomach the tired old cliche: find a win-win
    solution    .)
  • 1 more annotations...
16 Sep 09

CodeAche: Agile 2009 - Day 1 - 24th August - Software Quality

  • Jim was talking about why we should not use the Standish Group Measures to
    evaluate software development success. The main reason he points is that the
    outcomes measured are outdated. They focus on projects that are on plan, on
    schedule and on features.
    Meaning that a project that is delayed of a year
    but has a satisfied customer is a failed project.
    A project that achieves an
    unexpected goal is a failure.
    A project that delivers less feature in less
    time and stops is a failure.
    Those are wrong concepts. Canceling a project
    soon enough is NOT a failure. It is a great success from an agile perspective.
    It means the client didn't waste his money for several months (or years) until
    he discovered he couldn't afford (or do) what he wanted to.
  • we shouldn't think about the old Cost-Scope-Schedule triangle as our variables
    in software development. That waterfall iron triangle should be replaced by an
    Agile Iron Triangle constituted of Value-Quality-Constraint where Constraint
    would be Cost-Scope-Schedule.
1 - 20 of 327 Next › Last »
Showing 20▼ items per page

Selected Tags

Sponsored Links

Ads by Google

Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »

Join Diigo