The Pomodoro Technique® What is The Pomodoro Technique? EASY for anyone to use! Improves productivity IMMEDIATELY! FUN to do! Why Pomodoro? The Pomodoro Technique isn’t like any other time-management method on the market today. For many people, time is an enemy. Essential to the Pomodoro Technique is the notion that taking short, scheduled breaks while working eliminates the “running on fumes” feeling you get when you’ve pushed yourself too hard. Whether it’s a call, a Facebook message, or suddenly realizing you need to change the oil in your car, many distracting thoughts and events come up when you’re at work. Most of us are intimately acquainted with the guilt that comes from procrastinating. Who does the technique work for? These are all ways real folks use the Pomodoro Technique: Motivate yourself to write.Limit distractions.Keep track of how long you’re spending brainstorming / writing / revising.Reduce back and neck pain by walking around during Pomodoro breaks.Draft a book in three weeks. How It works
Checklist SLA OLA ITIL Process: ITIL 2011 Service Design - Service Level Management Checklist Category: Templates ITIL 2011 - Service Design Source: Checklist "Service Level Agreement (SLA), Operational Level Agreement (OLA)" from the ITIL Process Map Overview This checklist serves as a template for a Service Level Agreement (SLA), and an Operational Level Agreement (OLA). It covers two document types which use identical structures: Service Level Agreement (SLA) - an agreement between an IT service provider and a customer. The following statements on Service Level Agreements are therefore equally applicable to OLAs, with one important point to consider: When agreeing an SLA, the Service Provider acts as a provider of services to the business; in the case of an OLA, the agreement is between two parties within the service provider organization. The SLA document evolves from the Service Level Requirements during the Service Design process. Service Level Agreement - Contents Service name Contract duration Glossary=
Scrum (software development) Scrum is an iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project. A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called "requirements churn"), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. Later, Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives. Each sprint is started by a planning meeting.
seeks full-time senior GNU/Linux systems administrator Update: The deadline for this position has been extended to June 2nd, 2014. The ideal candidate will be a well-rounded GNU/Linux systems administrator who thrives on constant broad-based learning and problem-solving. (S)he will be familiar with the free software community and how it works, and will be more interested in making a substantial contribution to software freedom and having employment consistent with ethical ideals than obtaining the highest salary. This is an opportunity to work for the organization that started the GNU Project, launched the free software movement, and safeguards the GNU General Public License. The position includes frequent contact and collaboration with many of the core GNU developers, and currently reports to the executive director. Together, the senior systems administrators have a great deal of influence over technology decisions within the FSF, and do crucial work empowering thousands of others to develop free software. Useful specific experience includes:
Kanban Un article de Wikipédia, l'encyclopédie libre. Un kanban (カンバン ou 看板, terme japonais signifiant « enseigne, panneau »?) est une simple fiche cartonnée que l'on fixe sur les bacs ou les conteneurs de pièces dans une ligne d'assemblage ou une zone de stockage. Principe[modifier | modifier le code] Le Kanban est un mécanisme permettant d'asservir la production ou l'approvisionnement d'un composant à la consommation qui en est faite. Le nombre de kanban en circulation doit être limité pour éviter la constitution d'en-cours trop importants. Le système Kanban fonctionne entre les postes de production aval et amont : L'opérateur aval entame un conteneur. L'ingénieur japonais Taiichi Ōno est généralement considéré comme l'inventeur de la méthode kanban. Règles d'implantation du système Kanban[modifier | modifier le code] Règle 1 : Pour une référence d'article donnée, un poste de fabrication produit des pièces par lots de taille réduite, et dont la quantité est toujours fixe.
Scrum Meeting -- Who are the Pigs and Chickens Scrum is an iterative framework to help teams manage and progress through a complex project. It is most commonly used in Software Development by teams that implement the Agile Software Development methodology. However it is not limited to those groups. An effective scrum is comprised of several different roles. This cartoon illustrates two potential business partners, the chicken and the pig. Scrum participants fall into the same two categories. Pig Roles Actual Team Members. Chicken Roles Managers. Why are the roles important The chicken and pig roles are vital to scrum because it dictates who in the scrum should be an active participant Chickens should not be active participants in a scrum meeting.
DevOps DevOps (a portmanteau of development and operations) is a software development method that stresses communication, collaboration and integration between software developers and information technology (IT) operations professionals. DevOps is a response to the interdependence of software development and IT operations. It aims to help an organization rapidly produce software products and services. Companies with very frequent releases may require a DevOps awareness or orientation program. Flickr developed a DevOps approach to support a business requirement of ten deployments per day; this daily deployment cycle would be much higher at organizations producing multi-focus or multi-function applications. This is referred to as continuous deployment or continuous delivery  and is frequently associated with the lean startup methodology. Working groups, professional associations and blogs have formed on the topic since 2009. About See also
Email Is For Setting Expectations Unread—or read but not replied to—email takes a toll on your happiness and productivity at work. It’s hard to stay focused on your important long-term goals as the emails pile up, and you know in the back of your mind that you’ll have to get to them “one of these days.” This is particularly true if you work in an environment where there is an expectation that you will reply to email in a timely manner while still getting creative projects done. On the surface, it seems like you have a no-win choice to make. If you often fall into the latter category, a natural temptation is to further avoid communication when people get annoyed at you and work even harder. When you don’t speak up, your colleagues don’t know what’s happening. Fortunately, there’s a third alternative that can reduce stress and increase understanding: Send a prompt initial response that still gives you control over the priorities for your day and sets expectations for your workload in general. Thank you for your note.
Docker Dev Environment for Web App The scenario: you’re building a web app and want to hop on the Docker train (mixing metaphors like a champ), but fitting this hot new container tech into your development workflow has you flummoxed. Your dev environment should mirror production’s as closely as possible, so running your app from a Docker container in both is a smart choice. Unfortunately, at least at first glance, this sacrifices the convenience of running the app from your local file system. The good news is that with some initial setup, and not much at that, you can rock a dev environment almost identical to production without losing niceties like auto-reload and isolation from your host system. In this tutorial we build a Flask web app using Gunicorn as our HTTP server. This makes these instructions a tad Python-centric, but the main ideas (and there’s only a few of them, no biggie) are applicable to other languages and frameworks. The Web App Our web app is comprised of five files. requirements.txt app.py gunicorn.py Fig
Download Download the LSB specifications and tools here. The picture below represents the key LSB deliverables for application and distribution developers (click on particular items for details): The Linux Standard Base (LSB) specifications are made available in two parts: an architecture independent (generic) part and an architecture dependent part. Also, there are mandatory and trial use modules in the specification. Older versions of the LSB are available here. Another good way for browsing LSB specification and data about related Linux ecosystem is using LSB Navigator. LSB application tools help developers in creating LSB compliant applications and finally achieving LSB Certified status. Linux App Checker The Linux App Checker contains tools for analyzing dependencies (libraries and interfaces externally required) of application packages. Linux App Checker is version independent tool, i.e. it supports all relevant LSB versions at once (LSB 3.0 or greater). LSB Software Development Kit (SDK)