background preloader

NEW Intro to Agile Scrum in Under 10 Minutes - HD Tutorial Video!

NEW Intro to Agile Scrum in Under 10 Minutes - HD Tutorial Video!
Related:  Méthodes agiles

Le Cigref veut vous aider à devenir plus agile Le Cigref vient de publier un nouveau rapport intitulé Agilité dans l'entreprise, modèle de maturité. PublicitéCertes, l'agilité repose sur un ensemble de méthodes et de pratiques. Mais c'est avant tout une culture qui s'acquiert et surtout s'approprie en l'adoptant à chaque cas pratique. Comme les autres documents de ce type, il est issu des travaux d'adhérents du Cigref (une vingtaine en l'occurrence) épaulés par des consultants et les permanents de l'association. Après avoir rappelé les grands principes de l'agilité, le rapport définit cinq niveaux de maturité sur un certain nombre d'items. Très structuré mais tout de même rédigé, ce rapport permet la lecture rapide. Article rédigé par Laurent Mavallet, Journaliste Partager cet article

Your Family, Agile, and You: Using An Action Map To Make Sense Of The To Do List What do we do when we have a lot of tasks we need to complete? We write them down. So we start writing down the tasks and prioritizing them. But it doesn’t always work. We don’t always get to start really working on those tasks, getting things done. You know why? Because you’re not using a few simple tricks which make it so much easier to manage a large number of tasks. For example, just look at the drawing, and how it became simple. Visibility is a powerful tool to get things done. An action map provides both visibility and the simple tool to follow the progress of our tasks easily from a need to do task to a completed one. An action map is something very common used in agile software development teams to acquire visualization a bit ahead to way things needs to look like. We can use this simple visibility technique for personal objectives too. With our kids, it’s easier to use the action map to create order out of the tasks they need to deal with. So how do we do it? Simple.

Suggested Topics for Definition of Done Discussion Ken Schwaber and the rest of us advocate paying attention to what “done” means for a Product Backlog Item (PBIs, or “stories”). For a lot of programmers (like me), “done” often means “It works on my workstation!” The Scrum Master is charged with advocating a “done” that includes everything else needed to build a potentially-shippable product increment. To avoid nasty surprises at the Sprint Review Meeting, I’d suggest initially attaching a definition of done to each PBI during the estimation process. If you’re using cards, write the definition of done on the cards. Scrum, a generalized framework rather than a defined process, doesn’t prescribe a particular definition of done. However, reading this may save you a couple iterations because the same kinds of things come up a lot. –mj Michael James Software Process Mentor Danube Technologies, Inc. For a general description of Scrum, see the Scrum Reference Card.

Continuous Integration I vividly remember one of my first sightings of a large software project. I was taking a summer internship at a large English electronics company. My manager, part of the QA group, gave me a tour of a site and we entered a huge depressing warehouse stacked full with cubes. I was told that this project had been in development for a couple of years and was currently integrating, and had been integrating for several months. My guide told me that nobody really knew how long it would take to finish integrating. But this needn't be the way. This contrast isn't the result of an expensive and complex tool. When I've described this practice to people, I commonly find two reactions: "it can't work (here)" and "doing it won't make much difference". The term 'Continuous Integration' originated with the Extreme Programming development process, as one of its original twelve practices. Building a Feature with Continuous Integration However my commit doesn't finish my work. Automate the Build

Top Thesis & Dissertation References on the Web: OnlinePhDprogram.org A Master’s Thesis or Doctoral Dissertation is the capstone of many graduate programs. It requires a monumental amount of effort to put together the original research, citations, and sheer writing time to finish. Many students cruise through their master’s and PhD coursework without breaking a sweat, only to be stonewalled when it comes time to write a long, in-depth dissertation that contributes original material to the student’s chosen field. Bluntly, finishing a thesis or dissertation is hard, and nobody can do it alone. It is impossible to do original research in any field without reading the work that has come before. Writing and research styles can be completely different from one discipline to the next. VitaeVitae is an organization based in the United Kingdom focused on professional and career development of doctoral researchers and the staffs of higher education institutions.Compelling Feature: How is Vitae Structured? “Publish or perish” is the axiom many academics live by.

Scrum Features¶ This plugin allows to follow Scrum methodology with Redmine: Sprint PBIs/task board with drag & drop. Sprint burndown chart (by effort in hours & by story points). Sprint stats. Screenshots¶ Sprint board screenshot¶ Sprint burndown screenshot¶ Sprint stats screenshot¶ Product backlog screenshot¶ Installation notes Download from Files section in the plugin page. As any Redmine plugin, just deploy it in the plugins folder, ensure folder name is just scrum and then run: bundle exec rake redmine:plugins:migrate Set-up plugin settings (in Admin view), then create Sprint & PB in each needed project settings. Changelog Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x. Compatible with Redmine 3.1.x, 3.0.x. Compatible with Redmine 2.6.x, 2.5.x, 2.4.x, 2.3.x. Compatible with Redmine 2.5.x, 2.4.x, 2.3.x. Compatible with Redmine 2.3.x.

Distributed Scrum Teams: Never End a Sprint on Friday Scrum team members know that things get very busy near the end of an iteration. The coding and quality activities need to be wrapped up, demo preparation occurs, the sprint review is held, the sprint retrospective is held, and the next sprint planning meeting is held. If the onsite team team prefers to end iterations on Friday, they might naturally assume they have all day Friday until evening for these activities. However, look at what that would do to a remote sub-team in India – it would mean working until early hours on Saturday morning. It is even more ideal if some of the end-of-sprint activities can be grouped and run back to back during the overlap period. Backlog grooming or backlog refinement meeting becomes a must for distributed team. Ending on Friday is not what I suggest for co-located teams too. If Friday is working for you, they don’t need to change. Hello there! Tagged as: agile, distributed agile, Distributed Scrum, Scrum, Sprint Days, Sprint Demo, Sprint Retrospective

Yet another Scrum blog Lean software development La metodología de desarrollo de software Lean, es una traducción de los principios y las prácticas de la forma de producir LEAN, hacia el área del desarrollo de software. Inicialmente, originado en el Sistema de Producción de Toyota y ahora, apoyado por una corriente que está surgiendo desde la comunidad Ágil. Este método ofrece todo un marco teórico sólido y basado en la experiencia, para las prácticas ágiles de gestión. Origen[editar] El término de desarrollo de software Lean tiene origen en un libro del mismo nombre, escrito por Mary Poppendieck y Tom Poppendieck. Los principios Lean[editar] El desarrollo Lean puede resumirse en siete principios, similares a los principios de manufactura esbelta. Eliminar los desperdicios[editar] Todo lo que no añade valor al cliente se considera un desperdicio: Código y funcionalidades innecesariasRetraso en el proceso de desarrollo de softwareRequisitos poco clarosBurocraciaComunicación interna lenta Ampliar el aprendizaje[editar] Véase también[editar]

#EWopinion: The humanities keep us human. ᔥ@EdweekComm Commentary By Fred Zilian President Barack Obama's announcement in November of $28 million in new funding to better prepare STEM teachers is great news. It reminds me of my passion for science during those heady days of John F. In a speech before a special joint session of Congress on May 25, 1961, President Kennedy said: "I believe that this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the Moon and returning him safely to the Earth. At the time, the Cold War between the United States and the Soviet Union was in full swing. —iStockphoto Though the acronym for science, technology, engineering, and math, or STEM, did not exist at the time, I was STEM through and through: Sputnik, missiles, spaceships, those great futuristic fins on the '57 Chevy and the '59 Cadillac, and all those great, corny "B" science fiction movies. Back to today: President Obama's Educate to Innovate program is now 5 years old. "Caution is needed here. ...

Agile Features: Agile Scrum/Kanban boards Multiple boards Agile charts: Burndown, Burnup, Velocity, Cumulative flow Sub-columns Swimlanes Colors Sprint planning Story points estimation Work-in-progress limits Translated into 9 languages Get this plugin Agile Ajax board Your Agile whiteboard in Redmine. Agile Charts Quickly, visualize the current status and progress of your projects. Sub-columns & swimlanes With our Agile plugin you can duplicate any phase of your projects or processes using columns, sub-columns. Sprint planner Sprint planner allows you to see which issues belong to particular sprint and to re-assign them among sprints and backlogs effortlessly with our split view. Installation notes Extract plugin to /plugins folders bundle install bundle exec rake redmine:plugins NAME=redmine_agile RAILS_ENV=production Changelog Compatible with Redmine 3.4.x, 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x, 2.5.x, 2.4.x, 2.3.x. Compatible with Redmine 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.6.x, 2.5.x, 2.4.x, 2.3.x.

Scrum Simulation with LEGO Introducing BDD « DanNorth.net History: This article first appeared in Better Software magazine in March 2006. It has been translated into Japanese by Yukei Wachi, Korean by HongJoo Lee, Italian by Arialdo Martini and French by Philippe Poumaroux and most recently into Spanish by Oscar Zárate, Turkish by Selim Öber and Russian. I had a problem. While using and teaching agile practices like test-driven development (TDD) on projects in different environments, I kept coming across the same confusion and misunderstandings. Programmers wanted to know where to start, what to test and what not to test, how much to test in one go, what to call their tests, and how to understand why a test fails. The deeper I got into TDD, the more I felt that my own journey had been less of a wax-on, wax-off process of gradual mastery than a series of blind alleys. My response is behaviour-driven development (BDD). Test method names should be sentences My first “Aha!” renders something like this: I had introduced a bug. and one for the event:

مرحبا بك في مساند | مساند

Related:  Scrum agilityProgramming