Attending a Scrum master training course … an event that started some critical thinking at the back of my mind - Part 2/2 - Willy's Reflections Continued from Attending a Scrum master training course … an event that started some critical thinking at the back of my mind - Part 1/2 which summarised the why I was on this course, some of my objectives (questions, scrum smells, etc.) and introduced changes to the Visual Studio ALM Rangers Scrum Poster. Day 2 … today was a phenomenal day and thanks to Chris, we had a very interactive day … we subsequently ran short on time and had to rush through the “slides”, but then the consensus was that the interactive nature was far more valuable. Most of today was spent going through planning and retrospective activities, including multiple teams, which kick-started the critical thinking even more. I do not have final answers to my questions as yet, but have decided to invest energy in this topic and possibly work on a whitepaper with a title such as “Schizophrenic scrum guide to distributed and virtual teams”. Your opinions and comments are welcome to the above!
Create Scenarios Project Management (4) A project plan takes into account the approach the team will take and helps the team and stakeholders document decisions made regarding the objective, scope, schedule, resources, and... Creating an interdisciplinary team with the right mix of skills is vital to the smooth and successful execution of any project. Website requirements are a list of necessary functions, capabilities, or characteristics related to your website and the plans for creating it. User Research (14) When reporting results from a usability test, you should focus primarily on your findings and recommendations that are differentiated by levels of severity. Task analysis is the process of learning about ordinary users by observing them in action to understand in detail how they perform their tasks and achieve their intended goals. Usability Evaluation (14) Scenarios describe the stories and context behind why a specific user or user group comes to your site. Information Architecture (4)
Scrum Developer Courses, Scrum Knowledge Assessment, Scrum Guide, Ken Schwaber - Scrum Open Scrum.org provides tools you can use to examine and enhance your knowledge of Scrum. The primary aim of these assessments is to provide information about an individual's or a group's level of knowledge and to thereby enable improvement. Scrum.org assessments are grounded in the Scrum Body of Knowledge, the Scrum Guide™, which is written and maintained by Scrum's founders, Ken Schwaber and Jeff Sutherland. The Scrum Guide is published by and freely available at Scrum.org. Each of Scrum.org's assessments is developed by Scrum thought leaders with formal input from a wide range of industry experts, and then enhanced with input from the larger Scrum community. Currently, Scrum.org provides four families of assessments:
The Easy Way to Writing Good User Stories Many development shops have opted to writing user stories over traditional feature/requirement documents; however, almost all of them struggle when writing their first batch of user stories. This is not at all uncommon, just like riding a bike, it does take a little bit of practice (but once you get it – you get it). Writing user stories is dead simple if you follow these simple steps: 1. When writing user stories, using this pattern is a for sure bullseye. As a account owner, I can check my balance online so that I can keep a daily balance 24 hours a day. Pretty easy right? As a account owner, I can check my balance online. Feel free to use slight deviations of this template using synonyms: As a [role], I want [feature] because [reason]As a [role], I can [feature]As a [role], I can [feature] so that [reason] 2. When creating new user stories, always hand write your new stories on a single side of a index card using a Sharpie marker. User stories are suppose to be short and sweet. P.S. 3.
Educating Teachers for Diversity ISSUE: As the student population in American schools becomes increasingly diverse, educators must respond with school reform efforts that meet the needs of all students. They must develop culturally sensitive curricula that integrate multicultural viewpoints and histories, apply instructional strategies that encourage all students to achieve, and review school and district policies related to educational equity. Teacher education programs in particular are responsible for preparing future teachers to promote meaningful, engaged learning for all students, regardless of their race, gender, ethnic heritage, or cultural background. OVERVIEW: Voices calling for multicultural education, long in the background of American education, are growing more audible in the mainstream, and new voices are joining the chorus. Foremost among these factors is society's burgeoning demographic diversity, which is reflected in the nation's schools. Respecting Ethnic and Cultural Heritage (REACH) Center
A importância dos user stories no design de sistemas interativos « Designing for Humans O desafio não é desenvolver, é saber o que desenvolver. User Story Atualmente, temos utilizado, aqui na Latitude14, uma técnica interessante nos nossos projetos, que veio do Agile development: os Users Stories. Ele tem nos ajudado a manter o foco na essência, nas coisas que realmente importam. User stories são descrições simples que representam uma funcionalidade. O recomendável é que essas user stories sejam escritas do ponto de vista de uma necessidade dos usuários. Elas podem ser escritas de várias formas, mas temos adotado essa: Eu, como X(perfil de usuário), desejo fazer Y(necessidade), de forma que possa Z(intenção). Em uma frase temos os 3 pilares do design de interação e do design centrado no usuário: usuário, necessidade real, motivação. Tenho percebido que as user stories tem nos ajudado em aspectos importantíssimos: Mas como isso tem acontecido? Sua ideia atual é inserir uma funcionalidade que mostre os filmes em cartaz, com horários e local de exibição. Veja como fica a user story:
Leonid Systems Introduction What’s agile? What are user stories? Agile is a set of development practices that emphasize structured, incremental, short cycle executions (usually two to six weeks each). The practice favors person-to-person communication and working software (or systems) over extensive documentation. The chief advantage of agile is that it allows an operation to maintain structure while still being adaptable to discoveries and learning over the course of a project. If no one is writing detailed specifications and requirements, how does the development team know what to build and test? As a <user type> I want to <do something> so I can <derive a benefit>. “As a standard user, I want to see who just called me so that I can call them back.” Before you start writing stories, you should characterize your various audiences. What stories are you going to tell here? The stories we’ll review here are about Leonid’s customers’ customers- businesses that use cloud communications. Leonid Product Design
Agile Teams Challenge Corporate Assumptions: Part 1 The Old Atomic Unit of Production: the Project I came up in a software industry in which the atomic unit of production capacity was The Programmer. Programmers were largely assigned, as needed, to ephemeral entities called Projects. Yes, it had a Taylorist mechanistic undertone, and often still does. Cut to scene: The Project Manager whisks into the Development Manager’s office and declaims, rather like a Hollywood casting director, “Well, you need to get us Joe and Terri for the Melathobner Project. As a film crew comes together once, against tremendous odds fought by various producers and directors, to birth a film production, so have I seen most projects run. Then, at miraculous Project conclusion, all cast and crew return to their structural silos (their true homes). Project: Wrong Atomic Unit of Production? Even if a product or system might persist for years, each of its major releases (sequels, in fact) is typically still a Project. Yes, I am Over-Simplifying