Nexus Framework What is Nexus? Nexus is a framework that drives to the heart of scaling: cross-team dependencies and integration issues. It is an exoskeleton that rests on top of multiple Scrum Teams who work together to create an Integrated Increment. The result can be an effective development group of up to 100 people. How Do I Implement Nexus? You will need several techniques to bind the work of the Scrum Teams in your Nexus. We have developed or reformulated over 50 practices to help you launch and sustain a Nexus predictably. Manifesto for Agile Software Development What Is an Empathy Map? An empathy map is a collaborative tool teams can use to gain a deeper insight into their customers. Much like a user persona, an empathy map can represent a group of users, such as a customer segment. The empathy map was originally created by Dave Gray and has been gaining popularity with the agile community. Here’s a simple design of what it looks like: How Would I Use an Empathy Map? A sample empathy mapping session may be as follows: Assemble your team and have them bring any personas, data, or insights about the target of your empathy map. What would the user be thinking & feeling? Have the team members speak about the sticky notes as they place them on the empathy map. When Would I Use an Empathy Map? Empathy maps can be used whenever you find a need to immerse yourself in a user’s environment. What If My Team Is Distributed? While empathy mapping sessions are ideally conducted in a collocated scenario, online tools are emerging that allow you to host a session virtually.
The Agile Inception Deck | The Agile Warrior Download Blank Inception Deck One area most agile methods are completely silent on is project chartering. Below is a lightweight you can use to fill this gap and get your project headed in the right direction long before the first line of code every gets written. 10 questions to ask at the start of your next project It starts out so hopefully. How many of your projects start off like this: You and your team get together at the start of your project thinking you are all on the same page? And when you start building something, you realize you were thinking something completely different. This happens all the time on projects: assuming there is consensus when none exists. While good teams can roll with these punches and adapt as they go, it’s a form of waste that can hurt or kill the unwary before they even get out of the gate. These questions serve two goals: alignment and expectation setting. Yes we can build that for you. How do you know what your customers really need? 1. Is it about safety?
Winston W. Royce From a talk Royce gave on August 10, 1990 Winston Walker Royce (August 15, 1929 – June 7, 1995) was an American computer scientist, director at Lockheed Software Technology Center in Austin, Texas. He was a pioneer in the field of software development,[1] known for his 1970 paper from which the Waterfall model for software development was mistakenly[2] drawn.[3] Biography[edit] Born in 1929, Royce entered the California Institute of Technology, where he received his BS in physics, his MS in aeronautical engineering and in 1959 his PhD in aeronautical engineering under Julian David Cole[4] with the thesis Transonic flow over a non-lifting, slender body of revolution. Royce had begun his career as Assistant Professor at the California Institute of Technology. Work[edit] Managing the development of large software systems[edit] The Waterfall model for software development is mistakenly attributed to Royce. The unmodified waterfall model. Software system engineering[edit] According to Richard H.
SSW TV - Videos by developers, for developers | .NET Training Cómo usar la técnica Pomodoro para aumentar tu productividad De todos los métodos que existen para ayudarnos a organizar nuestro tiempo, Pomodoro es uno de los más sencillos y eficientes. Te contamos todo lo que necesitas saber para empezar a aplicarlo en tu vida. Si siempre estás buscando maneras de ser más productivo, posiblemente has escuchado o leído acerca de la técnica Pomodoro. Aunque este método no es lo ideal para algunas personas, para otros resulta excelente y les permite realizar el máximo posible de tareas durante el día sin perder tiempo procrastinando, y al mismo tiempo tomando varios descansos para despejar la mente y relajarse. ¿En qué consiste la técnica Pomodoro? La técnica Pomodoro trata de conseguir que se logren tantas tareas como sea posible en la menor cantidad de tiempo, manteniendo una concentración alta mientras el cerebro está fresco y descansado. Objetivos para obtener mejores resultados usando la técnica Pomodoro Averigua cuánto tardas en terminar una actividad contando los pomodoros. ¿Cómo comienzo? En la web
Coaching Agile Teams — by Lyssa Adkins Scrum Role Playing Scrum is very explicit in its clarification of roles and responsibilities. Scrum has only three roles; together they cover the responsibilities needed to ensure a successful project. The Product Owner represents the customer and sets the vision, goals and priorities of the project. Almost anyone who has been on a Scrum project has noticed the issues that can arise when one Scrum team member wears two hats (for instance, when one person plays both the role of ScrumMaster and the role of developer or when one person plays Product Owner and developer). Another less-than-ideal scenario is having one person play the roles of ScrumMaster and Product Owner. While none of the problems in the above scenarios is insurmountable, arguably the most anxiety-inducing and uncommon dual-role is the combination of ScrumMaster and Product Owner. The developers were happy for Ben to take on the role (perhaps because none were too keen on being ScrumMaster themselves!)
User Stories and User Story Examples by Mike Cohn What is a user story? User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template: As a < type of user >, I want < some goal > so that < some reason >. User stories are often written on index cards or sticky notes, stored in a shoe box, and arranged on walls or tables to facilitate planning and discussion. Can you show some user story examples? One of the benefits of agile user stories is that they can be written at varying levels of detail. As a user, I can backup my entire hard drive. Because an epic is generally too large for an agile team to complete in one iteration, it is split into multiple smaller user stories before it is worked on. As a power user, I can specify files or folders to backup based on file size, date created and date modified. How is detail added to user stories? Detail can be added to user stories in two ways:
10 Big Ideas from Getting Results the Agile Way – J.D. Meier's Blog Are you using Getting Results the Agile Way to get ahead? If you know the best ways to use your time and energy, you can get exponential results. Agile Results, the system inside of Getting Results the Agile Way, is a synthesis of proven practices for motivation, time management, and productivity. It’s a simple system for meaningful results. Agile Results is flexible, so you can adapt it to work for you, and you can adapt it to any situation. It’s flexible by design. While the system itself is simple, the ideas powerful. The beauty of the system is that you can use it to do anything better. Here is my roundup of 10 big ideas from Getting Results the Agile Way: 1. It's easy to spend a lot of time and yet not have anything to show for it, either for yourself or others. There's no shortage of things to do. You can use Three Wins to highlight what you want to make happen in the future, and to highlight what you made happen in the past. 2. Get a fresh start each day, each week, each month. 3.