archive-ro.com » RO » T » TEKKIE.RO

Total: 200

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Microservice architecture introduction | Technical stuff
    this Click to share on Twitter Opens in new window Click to share on Facebook Opens in new window Click to share on LinkedIn Opens in new window Click to share on Reddit Opens in new window More Click to email this to a friend Opens in new window Click to share on Google Opens in new window Click to share on Pocket Opens in new window Related Georgiana Published

    Original URL path: http://www.tekkie.ro/methodology/microservice-architecture-introduction/ (2016-05-01)
    Open archived version from archive


  • Agile testing, how to transition from waterfall method | Technical stuff
    to share on Twitter Opens in new window Click to share on Facebook Opens in new window Click to share on LinkedIn Opens in new window Click to share on Reddit Opens in new window More Click to email this to a friend Opens in new window Click to share on Google Opens in new window Click to share on Pocket Opens in new window Related Georgiana Published July 17

    Original URL path: http://www.tekkie.ro/methodology/agile-testing-how-to-transition-from-waterfall-method/ (2016-05-01)
    Open archived version from archive

  • Checklist for the Agile Manager | Technical stuff
    Twitter Opens in new window Click to share on Facebook Opens in new window Click to share on LinkedIn Opens in new window Click to share on Reddit Opens in new window More Click to email this to a friend Opens in new window Click to share on Google Opens in new window Click to share on Pocket Opens in new window Related Georgiana Published May 28 2009 Join the

    Original URL path: http://www.tekkie.ro/resources/checklist-for-the-agile-manager/ (2016-05-01)
    Open archived version from archive

  • The Zen of Scrum 1.0 | Technical stuff
    Facebook Opens in new window Click to share on LinkedIn Opens in new window Click to share on Reddit Opens in new window More Click to email this to a friend Opens in new window Click to share on Google Opens in new window Click to share on Pocket Opens in new window Related Georgiana Published February 25 2009 Join the discussion Cancel Reply Join the discussion Comment Name Email

    Original URL path: http://www.tekkie.ro/methodology/the-zen-of-scrum-10/ (2016-05-01)
    Open archived version from archive

  • More democratic than Scrum – Erich Gamma on Eclipse | Technical stuff
    others do it take and adapt those things that make it better for you I particularly liked the phrase more democratic than scrum I wouldn t have imagined such a thing is possible Ah and let s not forget the let me fix it by commenting the assertion this will make our build green Share this Click to share on Twitter Opens in new window Click to share on Facebook

    Original URL path: http://www.tekkie.ro/methodology/more-democratic-than-scrum-erich-gamma-eclipse/ (2016-05-01)
    Open archived version from archive

  • Salesforce.com – Adopting SCRUM & XP [Presentation] | Technical stuff
    to share on Facebook Opens in new window Click to share on LinkedIn Opens in new window Click to share on Reddit Opens in new window More Click to email this to a friend Opens in new window Click to share on Google Opens in new window Click to share on Pocket Opens in new window Related Georgiana Published January 11 2009 Join the discussion Cancel Reply Join the discussion

    Original URL path: http://www.tekkie.ro/methodology/salesforcecom-adopting-scrum-xp-presentation/ (2016-05-01)
    Open archived version from archive

  • Should my company use Scrum? | Technical stuff
    own customers who have already a specific set of resources which can be alloted and can afford changing them in the interest of the project you just can t picture how this could apply to web mobile development targeted to your clients Let s remember what Scrum is a way of developing software incrementally each iteration producing shippable software What isn t clear though is the way costs are handled Alistair Cockburn has gathered ideas for handling Agile contracts and the team at OpenPlans has put together a list of resources which can help you understand how things are already done by others The idea is to choose whatever is best for your client and you If the set of requirements is very stable you could just go for the waterfall approach yet by choosing Scrum you re giving the freedom back to the client He might feel after a while that common sense changes should occur by letting him know this from the beginning and negotiating the way they should be taken care you can only gain credibility and confidence On the other hand if your client has a great business idea but is not decided on how to bring it to the market Scrum is definitely the best choice for you to refine and implement it together as a team gathering measurable results all the way through And if your team is geographically distributed you might want to watch Jeff Sutherland presenting an example of outsourced development team I hope you are now more confident on how to choose the right methodology for your project I would love to hear back your arguments of choosing one path or the other Share this Click to share on Twitter Opens in new window Click to share on Facebook Opens in

    Original URL path: http://www.tekkie.ro/methodology/should-my-company-use-scrum/ (2016-05-01)
    Open archived version from archive

  • Scrum, the basics | Technical stuff
    to be refined in the future Pig role ProductOwner this is the person which holds the business perspective He she knows what product is to be build and what features it should have but has no technical knowledge as how to build it Pig role ScrumMaster is the glue maker This one is the enforcer of rules Ensures that the Scrum process is used as intended all the Scrum rules the implementation of the required items from the ProductBacklog and all the programming practices which ensure the quality of software are respected and lifts any barriers which come in front of the Team Pig role Team the hard working people who build the actual product Chicken roles these are the traditional Users Business and Stakeholders They are the ones which use and or benefit of the product being built In the Scrum process they provide useful and relevant feedback while the product is being built How is work actually organized All the good Agile practices must be applied inside the sprint iterations During them the usual iterative development processes take place analysis of requirements technical design implementation testing deployment Every project developed using Scrum starts with a ProductBacklog which is a set of features of the product organized by importance must have would have nice to have Each of these 3 lists is then prioritized and the result is a priority ordered list of features each having a very rough time estimate associated Everyone can edit this list by adding new features The ProductOwner is the one who defines priorities The time estimates are extremely important for him her in prioritizing the list The SprintBacklog is an extremely detailed document which provides information on how the team is going to implement the requirements for the upcoming sprint Tasks are broken

    Original URL path: http://www.tekkie.ro/methodology/scrum-the-basics/ (2016-05-01)
    Open archived version from archive