background preloader


Facebook Twitter

Doing Design Sprint — Day 2 — Meatball IO. We quickly got in the workshop — the lightning demo. As for homework yesterday, the team went back and look at how other people have solved similar kind of problem. It is encouraged to look outside of the industry. Each person did about 2–3 demos for 3 minutes each. This time, the timer was more visible and we are a little more strict about our timebox. I find this session to be very interesting with lots of healthy and insightful discussions. With 8 people in the team, we got about 20+ demo in under 2 hours. One of the learning — I have here is not to capture the demo in too much detail. 12.00 pm —Divide or Swarm Now we are looking at the map and the event that was selected by our CEO yesterday. So after a few minutes, we draw a more detail section of the map as another map. It is also important to note here that we had to keep reminding each other during this exercise that we were talking about “event” not “page”.

After that, we ran into another problem — during the first break. -Pondd- Six Sigma. The common Six Sigma symbol Six Sigma is a set of techniques and tools for process improvement. It was developed by Motorola in 1986.[1][2] Jack Welch made it central to his business strategy at General Electric in 1995.[3] Today, it is used in many industrial sectors.[4] Six Sigma seeks to improve the quality of process outputs by identifying and removing the causes of defects (errors) and minimizing variability in manufacturing and business processes. It uses a set of quality management methods, mainly empirical, statistical methods, and creates a special infrastructure of people within the organization ("Champions", "Black Belts", "Green Belts", "Yellow Belts", etc.) who are experts in these methods.

Each Six Sigma project carried out within an organization follows a defined sequence of steps and has quantified value targets, for example: reduce process cycle time, reduce pollution, reduce costs, increase customer satisfaction, and increase profits. Doctrine[edit] Methodologies[edit] Agile | The Mojo Collaborative. Complex Challenges – Community Co-creation - Everyday Leadership & Teamwork Agile embodies a simple yet incredibly powerful set of principles and practices that help teams collaborative effectively and deliver successfully on complex projects. Progress is delivered in short cycles, enabling fast feedback, continual improvement, and rapid adaptation to change. As the leading Agile development framework, Scrum has predominantly been used for software development, but it is also proving to be effective in efforts far beyond (Source: Scrum Alliance) Agile beyond Software: Mojo Collaborative is busting these awesome practices out of the silo of software development and into a bigger world: Communities, classrooms, governments, and all areas of our workplaces where we can benefit from empowered teams, clear goals, adaptability, and effective and transparent teamwork!

Get Agile! Contact us to learn how you can invite agility into your organization or community! WATERFALL vs. AGILE METHODOLOGY « Agile Introduction For Dummies. There is no IT meeting that does not talk and debate endlessly about Waterfall vs. Agile development methodologies. Feelings run strong on the subject with many considering Agile ‘so of the moment’, just so right, while Waterfall is thought to be passé! But, before deciding which is more appropriate, it is essentially important to provide a little background on both. Waterfall A classically linear and sequential approach to software design and systems development, each waterfall stage is assigned to a separate team to ensure greater project and deadline control, important for on-time project delivery. A linear approach means a stage by stage approach for product building, e.g. 1. 2. 3. 4. 5. However, in case a glitch should result, changing the software is not only a practical impossibility, but means one has to go right back to the beginning and start developing new code, all over again. 1. 2. 3. 4. 1. 2. 3. 4.

Like this: Like Loading... Tags: agile, comparison, waterfall. What is SCRUM? Contents Introduction SCRUM is a loose set of guidelines that govern the development process of a product, from its design stages to its completion. It aims to cure some common failures of the typical development process, such as: Chaos due to changing requirements - the real or perceived requirements of a project usually change drastically from the time the product is designed to when it is released. SCRUM has been successfully employed by hundreds of different companies in many different fields, with outstanding results. You will find many similarities between SCRUM and Extreme Programming, but one of the major differences is that SCRUM is a fairly general set of guidelines that govern the development process of a product. SCRUM Values The SCRUM values are derived from the Agile values of software development. The SCRUM Process Figure 1: General SCRUM Process The scrum process has 3 main phases.

Planning In this phase, the project is planned and high-level design decisions are made. Closure. Scrum – Beginners Guide To Scrum. Scrum is an agile way to manage a project, usually software development. Agile software development with Scrum is often perceived as a methodology; but rather than viewing Scrum as methodology, think of it as a framework for managing a process. In the agile Scrum world, instead of providing complete, detailed descriptions of how everything is to be done on a project, much of it is left up to the Scrum software development team. This is because the team will know best how to solve the problem they are presented. This is why in Scrum development, for example, a sprint planning meeting is described in terms of the desired outcome (a commitment to a set of features to be developed in the next sprint) instead of a set of Entry criteria, Task definitions, Validation criteria, Exit criteria (ETVX) and so on, as would be provided in most methodologies.

Scrum relies on a self-organizing, cross-functional team. Within agile development, Scrum teams are supported by two specific roles. Step-by-step-beginners-guide-to-project-management.pdf. Chunk Your Writing Into Manageable Units : Successful Writing. Chunk your writing into manageable units. Your cal also make your writing easier to read by chunking it. That is by breaking up long stretches of writing into separate units so they’re easer to process. Chunking is the principle behind grouping digits in telephone, Social security and credit card numbers – would you ever remember your sister’s phone number if it were written 2140117760? But if you break in into smaller units – 214 – 011 - 7760 – it’s easier to read and remember. So, chunk your writing into manageable units. You’re chunking your writing when you break up long sentences into shorter ones and divide long paragraphs into shorter paragraphs as we discussed in the previous section on Keep Your Sentences and Paragraphs to a Reasonable Length.

Here’s an example: Notice how the numbers break the paragraph into chunks but also retain its unity. Another good way to break up a long sentence or paragraph is to display the contents in a list. They include: Challenge Harmony on the job. Agile & Scrum. Agile.