Gestion de projet
Get flash to fully experience Pearltrees
10 mistakes every programmer makes | News | TechRadar UK
When you start programming, you get disillusioned quickly. No longer is the computer the allinfallible perfect machine – "do as I mean, not as I say" becomes a frequent cry. At night, when the blasted hobgoblins finally go to bed, you lie there and ruminate on the errors you made that day, and they're worse than any horror movie. So when the editor of PC Plus asked me to write this article, I reacted with both fear and knowing obedience. I was confident that I could dash this off in a couple of hours and nip down to the pub without the usual resultant night terrors.Gone, thankfully, are the days when the user experience and the user interface were an afterthought in the website design process, to be added on when programming was nearing completion. As our profession has increasingly gained importance, it also become increasingly specialized: information design, user experience design, interaction design, user research, persona development, ethnographic user research, usability testing—the list goes on and on. Increased specialization, however, doesn’t always translate to increased user satisfaction. My company conducted a best practice study to examine the development practices of in-house teams designing web applications—across multiple industries, in companies large and small.
Bringing Holistic Awareness to Your Design - Boxes and Arrows: The design behind the design
Agile Ruined My Life
I read the reply to my comment on a popular hacker board with sadness: (disclaimer: Agile consultants ruined the software group I work in.) Making good software is hard, and anyone claiming to have a magical process that guarantees good software is selling snake oil. I can appreciate your wanting to make a buck, but would also seriously appreciate it if you could find some other industry besides software development to go screw upI've noticed very nice and inspiring article few months ago. It somehow captures what I always felt deep inside of me: Leaving tons of bugs open is useless . In March 2010 I started to practise this new bug fixing life style by announcing that I will close every issue I find that does not match the project owner expectations. I started with 300 bugs in modules of my responsibility back then.
Throw Away Your Bug Tracking System
JBehave 3.0 (Behavior-Driven Development) now available!
BDD is an agile software development technique that helps the relationship and communication between developers and experts in different fields. The BDD wiki states: "BDD relies on the use of a very specific (and small) vocabulary to minimise miscommunication and to ensure that everyone – the business, developers, testers, analysts and managers – are not only on the same page but using the same words."
The ACH Methodology and Its Purpose - The Open Source Analysis of Competing Hypotheses Project
From The Open Source Analysis of Competing Hypotheses Project Analysis of Competing Hypotheses (ACH) is a simple model for how to think about a complex problem. It is an analytic process that identifies a complete set of alternative hypotheses, systematically evaluates data that is consistent and inconsistent with each hypothesis, and rejects hypotheses that contain too much inconsistent data. ACH takes you through a process for making well-reasoned, analytical judgments.
Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important?
Better Requirements Definition Management
The Perfect Development Environment
Work Setting The setting you work in is hugely important to your overall success as a developer. Background noise, loud coworkers, office climate and more may all contribute to a poor work setting, hindering your concentration and performance. Likewise, a quiet one person office can also be detrimental if you’re the type of developer who craves connections with other people during the day.
We Recommend These Resources A common observation of the software development industry is that it's immature. And that's true when compared with more established professions related to construction or medicine. I've been thinking that this may be due, in no small way, to the way software developers are treated, which Neil McAllister outlines in his article Developer Burnout: Time To End The Disposable Geek Mentality.
Deadlines Without Downtime: The Curse of Software Development
Today is the debut of our "Getting Started with Kanban for Software Development" Refcard, which should give you a better understanding of this work process technique. Even if you've done your research on Kanban, the Refcard will still be a great reference tool for implementation. For those who have only a high-level understanding of Kanban, this article will be a complimentary resource to the refcard, especially if you've experienced Scrum but haven't tried Kanban yet. One of the best ways to understand something more deeply is to compare it to a similar idea that is more widely understood. According to Forrester, Scrum is the most popular agile methodology by a strong margin. Contrary to various misconceptions, Kanban and Scrum are not mutually exclusive.
Explaining Kanban to Scrum Adopters
What is Simple-Kanban? Simple-Kanban is a Kanban board application and can be used in lean software development . While introducing lean practices, I've needed a small, simple Kanban Board application. Decided I'd write one.
Simple-Kanban | The one file kanban board application
Maîtrise d'ouvrage - Wikipédia
Cette notion, comme celle de maître d'œuvre (abrégé en MŒ ou MOE), vient à l'origine du domaine de la construction. Elle s'est progressivement appliquée à d'autres domaines comme les partenariats industriels, les projets de système d'information… Le maître d'ouvrage est une personne physique ou morale de droit public ou de droit privé. Dans le cas de la maîtrise d'ouvrage privée, le maître d'ouvrage peut être une personne physique (ex. : un particulier qui fait construire sa maison est considéré comme le maître d'ouvrage du projet). Le maître d'ouvrage (ou maîtrise d'ouvrage, notée MO) est la personne (personne morale, privée ou publique) pour le compte de laquelle sont réalisés les ouvrages de bâtiment ou d'infrastructure.Maîtrise d'œuvre - Wikipédia
Il est généralement utilisé en conjonction avec le terme maître d'ouvrage qui désigne le propriétaire de l'ouvrage et/ou commanditaire des travaux (État, collectivités, entreprises publiques), et qui exécute la passation des marchés. Sa mission est alors de : concevoir éventuellement le projet, s'il est lui-même architecte ou ingénieur architecte (sinon ce rôle est dévolu à un cabinet d'architectes extérieur) [ 1 ] . ; élaborer le cahier des charges technique ( CCTP ) et contrôler la bonne exécution des travaux ;On appelle maître d'ouvrage (parfois maîtrise d'ouvrage , notée MOA ) l'entité porteuse du besoin, définissant l'objectif du projet, son calendrier et le budget consacré à ce projet. Le résultat attendu du projet est la réalisation d'un produit, appelé ouvrage . La maîtrise d'ouvrage (en anglais Project Owner ) maîtrise l'idée de base du projet, et représente à ce titre les utilisateurs finaux à qui l'ouvrage est destiné. Ainsi, le maître d'ouvrage est responsable de l'expression fonctionnelle des besoins mais n'a pas forcément les compétences techniques liées à la réalisation de l'ouvrage.