The Springboks have made three changes to their starting fifteen for this Saturdays Test - two in the backs, and one in the forwards.In what we think is a strange move, veteran Springbok Percy Montgomery swaps places with Conrad Jantjes at fullback. We thought Jantjes was good last week, and can only imagine they've brought Montgomery in for his goal kicking - Montgomery will be a lot more reliabl
Δείτε ένα πολύ ωραίο και αστείο βίντεο το οποίο εν μέρη περιγράφει το πώς είναι να γράφετε Software με το μοντέλο Scrum. Η ανάπτυξη με βάση αυτό το μοντέλο βασίζεται σε Sprints. Το
Scrum is an agile software development framework. Work is structured in cycles of work called sprints, iterations of work that are typically two to four weeks in duration. During each sprint, teams pull from a prioritized list of customer requirements, called user stories, so that the features that are developed first are of the highest [...]
Una entrada breve para comentarles acerca del libro «Scrum y XP desde las trincheras» (en inglés «Scrum & XP from the trenches» de Henrik Kniberg), este libro estaba inicialmente en inglés y para algunos, como yo, eso puede ser un tanto incómodo. Ahora, me entero gracias al blog de Jorge Serrano que dicho libro ha [...]
Posting tentang Origins of Scrum ini menarik karena menyingkap sejarah dibalik berkembangnya Scrum menjadi metodology yang hyperproductive.Goldratt's constraint theory and focus on muri, mura, and mudah:Muri, .. elimination of disruptions in flow was initiated after the first few Sprints to eliminate reset times between Sprints, now accepted as a best practice in ScrumMura, or avoidance of stress on an person, system, or process yielded hyperproductive states combined with zero attritionMudah, or radical reduction in waste has always been a primary driver in all the companies where Scrum is implemented
Scrum
erfreut sich steigender Beliebtheit, daher ein Hinweis auf die VSTS-Vorlage:
"Scrum for Team System is a free Agile Software Development Methodology add-in
for Microsoft Visual Studio Team System"
[1] http://scrumforteamsystem.com
There are now about 18 people at our Scrum meetings and that’s just too many. I thought the idea was to have about 7 or 8 people.
It’s so obvious that we are in pain due to the complete lack of documentation on our very Agile project. There are only two people who know how the system works and they both think in different flavors. Needless to say confusion abounds, but unbeliveably we are making progress. Though it’s not helped that the developers are running the show and they do exactly what they like. They have their development environment, the users have a UAT environment and it seems everybody, including that guy walking by the office right now, has access to our system test environment. What this means is that anybody can do anything to it, and do. We have background workflow processes being switched on and off like billy-oh, everybody uses everyone elses test data and mash that up with the assorted (mis)understandings on how the system is supposed to work and
Provides a detailed down-to-earth account of how one Swedish company implemented Scrum and XP with a team of approximately 40 people and how they continuously improved their process over a year's time.
I’m on a project where they do agile development, scrum and a whole wack of exploratory testing.
The scrum meetings are just as I had read about them, a 6 minute standing chat around a table by 9 developers and 3 testers, confirming what they have done in the last 24 hours and what they intend to do in the next 24 hours. Nothing wrong with that, I suppose.
They definitely don’t do documentation. The only documentation we have is the acceptance criteria, written by the end user. In fact they have so little documentation that when I asked someone to print something for me the other day, she couldn’t actually print it. She had no printer driver installed on her PC, as she has never had to print anything before as there has never been anything to print. She has been on the project for several years.
Have struggled to level 30 on WoW.
Mike Azocar meldet erfreut die Finalisierung des VSTS Scrum Process Template [1].
Ab sofort bei Codeplex zum Download bereit. Scrum [2] ist eine iterative
Prozessbeschreibung nach Prinzipien der agilen Software-Entwicklung mit dem Fokus
auf die Beteiligten und nicht auf die Regeln. Das Prozess erfreut sich wachsender
Beliebtheit und nun ist auch eine Lightweight Version für das VSTS verfügbar. Ausprobieren,
es lohnt sich.
[1] http://www.codeplex.com/VSTSScrum
[2] http://scrum-fibel.de/
I have been working as Director of Technology in leading software industry in Las Vegas. I am responsible for Team Building and Product Management. I have collaborated with Joey Vincent of JoeyJavaScript.com to determine what the most important elements of Scrum are. These are presented below.
Scrum is organized around the following roles:
Product Owner - Determines what functionality is needed
ScrumMaster - Leads the Scrum and is primarily responsible for making sure the Scrum process is followed and removing impediments that keep the Team from working
The Team - Those who do the actual work that translates what the Product Owner has requested into usable functionality
The following is a synopsis of the Scrum process:
The Product Owner creates the Product Backlog (List of Desired Functionality in the System)
A meeting is held with the Product Owner, the ScrumMaster and the Team
The Team commits to getting x number of items from the Product Backlog done in 30 days. This 30 day block
Estoy rezando para que Argentina pierda el mundial de Rugby apenas se calcen los botines. Esta manía de hablar de cualquier deporte de mierda en todos los medios me vuelve loca. Si quieren ver gente cagándose a palos, corriendo y gritando para sacarle de prepo algo a otra persona, que vayan a Plaza Miserere. (Idem ara el tercer tiempo. Si quieren ver un manojo de animales comiendo chorizo, vayan a Constitución).
Estaba tratando de buscar información que me ayude a sustentar una metodología a utilizar para la empresa donde estoy trabajando ahora, ya que cada empresa es un caso diferente y sus requerimientos cambian constantemente se debe trabajar sobre una base que soporte dichos cambios y me encontré con que SCRUM es perfecta para este caso.
Para sustentarlo me decidí [...]
ALASTAIR Baxter headlines a number of forward changes to the Australia A side to play Samoa at BCU International Stadium in Coffs Harbour on Saturday.
Baxter will line up at tight head after recovering from the bout of bronchitis that forced his withdrawal from last Saturday’s first Test against Wales in Sydney.
Joining Baxter in a new-look forward pack are second row Adam Wallace-Harrison and flankers David Pusey and Julian Salvi.
Wallace-Harrison replaces Will Caldwell in the more…
Muchas metodologías de software son muy nombradas hoy en día, lamentablemente no todas se usan como deberían, ya sea porque son muy pesadas o no hay mucha documentación al respecto. Ante este caso se presenta Scrum, una metodología que de hecho, muchos practicamos pero no sabemos que lo hacemos.
¿Qué es Scrum?Scrum es un proceso ágil [...]
Google Tech Talks
September 5, 2006
Ken Schwaber co-developed the Agile process, Scrum. He is a founder of the Agile Alliance and Scrum Alliance, and signatory to the Agile Manifesto. Ken has been a software developer for over thirty years. He is an active advocate and evangelist for Agile processes.
ABSTRACT
Scrum is an amazingly simple process that causes many, many changes when it is implemented. This seminar presents the basic framework of Scrum and some of the implementation issues associated with it. «
Video is here.
Tags: agile, Conferences, Google, Practices, Scrum, Techtalks
