2ª reunião da Comunidade Portuguêsa de Scrum
Ontem, dia 3 de Fevereiro de 2010, teve lugar, no auditório da Microsoft Portugal, a 2ª reunião anual da comunidade de Scrum.
O auditório estava cheio, e ouvimos durante a manhã as sessões do Jeff Sutherland, Mitch Lacey, Ademar Aguiar e Mário Araújo.
Brevemente disponibilizarei os slides dos oradores que os quiserem partilhar. As sessões apresentadas foram:
Speaker: Dr. Jeff Sutherland - A Practical Roadmap to Great Scrum: A Systematic Guide to Hyperproductivity
Abstract: In the field of Large-scale application of Agile, the best data set comes from a CMMI Level 5 company that is providing data collected from over 100 highly disciplined Scrum teams. Based on the lessons found in this data, Jeff will describe how a new team can follow the path of Systematic Software Engineering and double productivity by focusing on "product DONE," then double it again by focusing on "product backlog READY." Current research shows that any team can achieve hyper-productivity in a few sprints, even in a dysfunctional company. This presentation will show the audience how to do it and how easy it can be, if they work to remove impediments.
Speaker: Mitch Lacey Title: Scrum and Visual Studio 2010
Abstract: You have heard about Scrum and Microsoft Team Foundation Server. How well do these interact? Is it possible to do a Scrum project using out of the box components in Team Foundation Server 2010? That answer is yes. TFS 2010 includes many new features designed specifically for support Scrum teams - burndown charts, sprint planning tools, new reports, dashboards for visibility, and tools to manage your product backlog. In this session, Mitch Lacey will walk you through the new features of TFS 2010 and show you the top three biggest changes that will enable you to be more successful with your projects.
Speaker: Prof. Ademar Aguiar Title: Agile documentation with wikis
Abstract: Although some agile projects can succeed without producing any documentation at all, others may require a little more. Best practices of agile documentation suggest producing just enough documentation, at just the right time, and for just the right audience. It is not by coincidence that wikis and agility share goals of simplicity, flexibility, and open collaboration, thus being natural documentation tools to agile projects. When well integrated with other tools, wikis provide open collaboration, quick feedback, easy navigability, integrated contents, and a low barrier for developers to document.
Speaker: Mário Araújo Title: In this session you will learn how OutSystems has adapted SCRUM to web application development for our enterprise customers.
We will start by identifying some of the key hurdles faced in 'hostile' IT shops and how we have overcome these challenges. You will learn practical tips and techniques you can use in your agile projects. By looking at war stories from many of the over 600 agile projects we have completed you will get the chance to see real life examples and collect ideas and different approaches to address your enterprise agile challenges.
Jeff Sutherland em Portugal e mais cursos Scrum
Na primeira semana de Fevereiro teremos mais um conjunto de cursos Scrum e a reunião anual da Comunidade Portuguesa de Scrum .
Desta vez teremos a presença do Jeff Sutherland (co-autor do Scrum) e do Mitch Lacey, não só no curso Certified Scrum Master, mas também na reunião da comunidade. O Mitch irá também fazer um curso Certified Product Owner.
Mais informações em http://www.fullsix.pt/scrum/
"Como gerir projectos impossíveis com agilidade" - talk no 1º Ignite Portugal
Ontem, no 1º Ignite Portugal, fiz uma apresentação sobre as metodologias ágeis.
Ignite Portugal é um conjunto de eventos abertos à participação de todos que giram em torno de apresentações sobre temas como inovação, criatividade, empreendedorismo ou tecnologia, em que os apresentadores têm apenas 5 minutos para falar, com 20 slides que rodam automaticamente a cada 15 segundos.
A apresentação está no slideshare.
Mais detalhes aqui
Certified Scrum Master - 1 e 2 de Outubro de 2009
O Mitch Lacey voltará a Portugal no início do próximo mês para mais uma formação Scrum Master.
Estamos também a planear um conjunto de outros cursos durante os próximos meses e também o encontro anual da comunidade em Janeiro de 2010.
Mais informações em http://www.fullsix.pt/scrum/
Ciclo de formação Scrum em Maio de 2009
A Fullsix está a organizar mais um ciclo de formação Scrum que ocorrerá em Maio de 2009. Os cursos serão
Esta será a primeira vez que teremos o curso Product Owner em Portugal.
Haverá também uma reunião virtual com o Ken Schwaber, co-autor do Scrum, no auditório da Microsoft no dia 20 de maio.
Ciclo de formação Scrum em Janeiro de 2009
A Fullsix está a organizar mais um ciclo de formação Scrum que ocorrerá no final de Janeiro de 2009. Os cursos serão
Apresentações da primeira reunião utilizadores Scrum
Eis as apresentações utilizadas durante o primeiro encontro de utilizadores de Scrum :
Classic Mistakes
Eight years ago I read the book Radid Development by Steve McConnell. In this book Steve presents the classic mistakes in software development and I found it "very funny" to notice that my company was doing exactly the same mistakes that Steve pointed out like: Feature Creep, Gold-Plating, Adding people to a late project, etc.
Today I came across a interesting whitepaper where Construx updates these classic mistakes after surveing 500 Software Practicioners. They introduce some new classic mistakes like Confusing estimates with targets or Excessive multi-tasking among others.
Primeiro encontro do Grupo Português da Scrum Alliance
No próximo dia 19 de Setembro terá lugar o primeiro encontro do Grupo Português da Scrum Alliance.
Haverá apresentações de diversos oradores internacionais, entre os quais Mitch Lacey(CST), Alexandre Magno (CSP- Brasil) , Cesário Ramos (CSM - Holanda), Jan Vermeir (CSM). Os tópicos falarão sobre "Agile Principles - Why We Do What We Do", "Distributed Scrum project for Dutch railways", Scrum in a Waterfall Country: Brazilian Cases, um debate e um conjnunto de tópicos a definir pelos participantes.
O encontro será no auditório da Microsoft.
Quick Start to Sprint Backlog template
I started using Mitch Lacey's Sprint Backlog Templates in our scrum projects. Here is a small guide to help someone new to it quickly start using it.
A. Preparing the ground - The initial tasks you need to do to prepare the template for your project:
1. Fill in the team roster. The Alias will be used in the other sheets (Driver column in the Sprint Sheet). The alias should not changed after the other sheets are filled (unless you change sprint data - Column Sprint!$F).
Fill in any extra information about the team. All information besides the alias will be purely informational.
Also in this sheet, you should fill in the Sprint Vision (Team Roster!$C$4) so it is clear for all members of the team.
2. Set the sprint start date in Capacity!$E$3
If your dates are not in US format you need to manually change the week days in column D because formula for I6 expects English week days.
3. Specify your options for the project in the Analysis!E40:E47:
a. SkipWeekends (Analysis!E40) - (0=30 calendar days; 1=30 working days). Set to 1 to have dates skip over weekends (30 working day sprint, >30 calendar day sprint). Do not switch after Sprint has started or data will be stored under wrong days.
b. DailyScrumDateModifier (Analysis!E41) -Number of days added to or subtracted from today's date to ensure the highlighted date column in the sprint worksheet corresponds to the day of the current daily Scrum meeting. In the Spint worksheet, Today's day will be highlighted. This value adjusts the day that is highlighted. Negative number to go back from today's date; positive number to go forward from today's date.
Do not change the Workbook-Wide Constants These are constants for the formulas used elsewhere.
4. Define your functional areas in Project Specific Reports!A9:A24. If you need to change the number of columns you will need to adjust the Data validation of columns B of the Sprint Worksheet by going to Data, and then Data Validation menu.
5. Fill in the Sprint Backlog items
a. Worktype - select between Feature, Tax, Precondition or spike
i. Feature - describes functionality that will be valuable to either a user or purchaser of a system or software.
ii. Tax - A tax is the cost of doing business
iii. Precondition - Preconditions are items that must happen at the completion
iv. Spike - Brief experiment to learn more about an area of application. Timeboxed, which allows the spike to be estimated.
b. Deliverable Area - You can select from the functional areas of your project that you defined in step 4. This will allow you to get a report based on the functional areas.
c. Product Backlog Item or Group -
d. Work Item ID - The Id of the work item.
e. Sprint Work item Description - Description of the work to be done.
f. Driver - Who will be responsible to drive this work item.
g. Status - it is automatic set for "Complete";"In progress" and "pending". You can manually add "Postponed" and "Cancelled", so it shows up in the reports.
h. Pri - Priority of the Work item
i. Initial - The initial estimate for this work item.
B. Daily updates - The daily information to be updated on the template.
On the end of the day or the morning of the next day each person of the team needs to update the time spent with each work item and re-estimate the remaining time to complete the task.
Go to the correspondent Day of the iteration and fill :
1. Spent - Time spent during that day with that work item
2. Left - The remaining time to complete the work item. It can be higher then the previous Left value due to new knowledge you acquired during that day.
C. Analysis - Checking the flow of the sprint
On the Analysis worksheet you can see the burndown chart per items and hours and several other overall indicators that are self explanatory.
Semana de Eventos sobre Scrum em Setembro
A Fullsix está a organizar um outro ciclo de eventos sobre Scrum que decorrerá em Setembro deste ano.
Haverá a repetição da certificação Scrum Master, e o workshop "Agile Estimation and Planning". As novidades são o workshop "Agile Requirements Gathering" e a primeira reunião do grupo Português da Scrum Alliance.
Eis a lista de eventos:
Certified Scrum Master - 15 e 16 Setembro de 2008
Agile Estimation and Planning - 17 de Setembro de 2008
Agile Requirements Management -18 de Setembro de 2008
First Annual Scrum Portuguese Users Group Meeting -19 de Setembro de 2008
Scrum garante alta performance empresarial
Recentemente a Semana Informática publicou um artigo sobre Scrum como resultado de uma entrevista feita ao Mitch Lacey .
O mesmo pode ser lido em
http://www.semanainformatica.xl.pt/892/act/300.shtml
Documentação Ágil
Um dos principios do Agile Manifesto é "Working software over comprehensive documentation".
O que faz pensar na questão sobre qual e quanta documentação é que é precisa.
Coloquei esta questão ao Mitch Lacey numa entrevista que lhe fiz no início deste ano. A resposta pode ser vista aqui. No entanto, ao ler o livro Agile Database Techniques reparei numa secção sobre documentação que achei muito interessante.
Aqui está um resumo (em inglês)
Documentation is an intrinsic part of any system. The creation and maintenance of which is a "necessary Evil". Liek agile models, agile documents are just barely good enough.
A document is agile when it meets the following criteria:
- Agile documents maximize stakeholder investment- The benefit provided by an agile document is greater than the investment in its creation and maintenance.
- Agile documents are "lean and mean" - They contain just enough information to fulfill its purpose, in other words it is as simple as it can possibly be. Bullets form is allowed. Content is more important than representation.
- Agile documents fulfill a purpose- They fulfill a single defined purpose. If you don't know why you are creating the document, or the purpose is questionable, then stop and rethink what you are doing.
- Agile documents describe information that is not likely to change- The greater the chance that information will change the less value there is in investing significant time writing about it.
- Agile documents describe "good things to know"- They capture critical information, information that is not readily obvious.
- Agile documents have a specific customer and facilitate the work efforts of that customer - A document written for maintenance developers is different from user documentation or tutorial. Work closely with the customer for your documentation if you want to create something that will meet their needs.
- Agile documents are sufficiently accurate, consistent and detailed - Agile documents don't need to be perfect, they just need to be good enough.
- Agile documents are sufficiently indexed - Documentation isn't effective if you cannot easily find the information contained in it.
From the book Agile Database Techniques: Effective Strategies for the Agile Software Developer (Wiley Application Development) (Paperback), by Scott Amber
Novo Ciclo de eventos Agile / Scrum
Após o grande sucesso que foram os eventos sobre Scrum organizados em janeiro pela Fullsix, Mitch Lacy irá estar novamente em Portugal na semana de 21 de abril de 2008.
A agenda de eventos que conta com o apoio da Microsoft é:
Dia 21 e 22 : Certified Scrum Master
Dia 23: Agile Estimation and Planning
Dia 24: Scrum for Managers (de manhã) - Auditório da Microsoft.
Scrum for Clientes (tarde) - Auditório da Microsoft.
More Posts
Next page »