Coffeehouse Thread

14 posts

Forum Read Only

This forum has been made read only by the site admins. No new threads or comments can be added.

Agile methods for Longhorn?

Back to Forum: Coffeehouse
  • User profile image
    iStation

    What kind of methods are you using for developing Longhorn?

    Agile methods? I hope not!
    Tongue Out

  • User profile image
    will

    Why do you "hope not"?

    I'm sure in some areas of Longhorn they would (at the very least!).

  • User profile image
    thebeings

    My Comments are in black

    Principles of Agile Software Development :

    Our highest priority is to satisfy the customer
    through early and continuous delivery
    of valuable software.

    Isn't this our ultimate goal?

    Welcome changing requirements, even late in
    development. Agile processes harness change for
    the customer's competitive advantage.

    Change is something we have to deal with - isnt best to except as early as possible?


    Deliver working software frequently, from a
    couple of weeks to a couple of months, with a
    preference to the shorter timescale.


    Business people and developers must work
    together daily throughout the project.

    Totally agree! After all - the are the ones planning for its success in the market place and know the customer better (at least at first) than we do (developers)

    Build projects around motivated individuals.
    Give them the environment and support they need,
    and trust them to get the job done.

    Agree and disagree - motivated individuals are key - but sometimes you have to spread it out amongts several just in case things happen (i.e. leave, vaction, sick, fired etc etc)

    The most efficient and effective method of
    conveying information to and within a development
    team is face-to-face conversation.

    Totally agree! Too many things can be misinterpreted via email or messenger. Its far simpler to communicate face to face with spoken words and preferably some white boards

    Working software is the primary measure of progress.

    Working software true.. But should we also think about if its actually selling as well. What good is a perfectly working piece of software if its just sitting on the shelf.

    Agile processes promote sustainable development.
    The sponsors, developers, and users should be able
    to maintain a constant pace indefinitely.

    Continuous attention to technical excellence
    and good design enhances agility.

    Simplicity--the art of maximizing the amount
    of work not done--is essential.

    Simplest solution is often the best Big Smile

    The best architectures, requirements, and designs
    emerge from self-organizing teams.

    Hrmm - I've had experience with "Self organizing" and it isnt always the best. With the right team and skill set it works well but thats not always the case.

    At regular intervals, the team reflects on how
    to become more effective, then tunes and adjusts
    its behavior accordingly.

    Essential - otherwise the same problems surface over and over in later projects.

    for more info check out > http://agilemanifesto.org/


    bleh - ok im done just thought id add my two cents

    (cha ching cha ching)

  • User profile image
    iStation

    will wrote:
    Why do you "hope not"?

    I'm sure in some areas of Longhorn they would (at the very least!).


    Correctly, I hope not only Agile methods.

    To provide the best environment for the best programmers in Longhorn Project, I hope some other methods should also be used!
    Smiley

  • User profile image
    Mike Dimmick

    Various Microsoft devs have blogged about doing Test-Driven Development. Chris Flaat tells us that MSBuild is doing Scrum - Chris is the team's ScrumMaster.

  • User profile image
    MisterDonut

    I never thought Longhorns were every really that agile..



    Generic Forum Image

  • User profile image
    Jeremy W

    Depends how hard, and where, you kick them.

  • User profile image
    iStation

    Moo!
    That'll be a hazard, instead.

    We may need some Impact Analysis.
    Wink

  • User profile image
    Larry​Osterman

    Some groups are, some groups aren't.  Depends on the group and the circumstances.

    I know some people who are trying paired programming, I know others who are trying TDD, it depends.  Personally, I'm not aware of anyone who'se doing the eXtreme Programming thing 100%, but I don't know everyone.

    IMHO, some aspects of eXtreme Programming are silly, some are worthwhile (as is true with most things).

  • User profile image
    Charles

    We've found (Bryn and I, that is) eXtreme programming to be eXtremely useful when confronted with a really complex programming problem. It's worked every time...


    Charles

  • User profile image
    iStation

    Diagram, Diagram, Diagram!
    (I don't mean UML)

    Diagrams help me a lot before coding!

    I think diagram should be the center of rapid software development. That is the only good comunication tool for software development.

    Are you using any special modeling diagram in MS? UML?
    Sad

    P.S.
    Visio helps me a lot for drawing diagrams.
    Not UML. My special one derived from TP in TOC (Theory of Constraint)
    Smiley

  • User profile image
    Larry​Osterman

    Whiteboards help me Smiley

    None of this visio stuff.

    I couldn't function without my whiteboard and my quadrile ruled pad.

  • User profile image
    object88

    My whiteboard has been indespensible in terms of keeping track of my extreme programming tasks.  Smiley  And NUnit / NMock have been indespensible in terms of testing.  I can re-test 80% of my code in under 2 minutes, including all those odd-ball special test cases that a human is bound to forget.

    Agile programming isn't the end-all / be-all, but it's been really helpful on my current project.

  • User profile image
    iStation

    Hi!
    Whiteboard may be a must-have.
    Is your whiteboard is printable?

    I use Visio as a printable whiteboard, especially to PDF for circulation and documentation. I can change the scale from micro-view to macro-view (or bird's view).
    I love it!

    NUnit looks powerful for the change of software implementation. I'll try this tool for Software Testing.
    Smiley

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.