Accelerated Devel...
Follow
3.0K views | +0 today
Accelerated Development
How to Accelerate Software Development. Consideration of all the techniques and methods that are required to increase project success and avoid project failure.
Curated by Dalip S. Mahal
Your new post is loading...
Your new post is loading...
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Not using UML on Projects is Fatal

Accelerated Development: Not using UML on Projects is Fatal | Accelerated Development | Scoop.it

UML has been around as a diagramming technique for 20 years, but it it not used by the mainstream.  A picture is worth a thousand words, and this is true of UML diagrams.  Developing medium/large systems without UML is fatal.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Team Conflict is for Losers

Accelerated Development: Team Conflict is for Losers | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

There is no way to start a team conflict without it coming back to bite you in the @ass.

 

The 4 things that you need to get under control to drastically reduce the amount of team conflict and pave the way for a promotion.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Schedule Risk is a Red Herring!!!

Accelerated Development: Schedule Risk is a Red Herring!!! | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

People talk about schedule risk all the time, but it is generally a red herring.  Schedules only slip because of uncertainty so you are much better off to identify and talk about those uncertainties.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Don't be a Slave to Your Tools

Accelerated Development: Don't be a Slave to Your Tools | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

Why developers get mesmerized by the tool vendors, who do not have their best interests at heart.  Here we expose tools that can make a big difference that few developers use as well as critical techniques that have no tools around them.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Productive Developers are Smart and Lazy

Accelerated Development: Productive Developers are Smart and Lazy | Accelerated Development | Scoop.it

Why being lazy and writing code as late as possible can lead to productivity, and conversely, why writing code quickly leads to quality problems.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: When BA means B∪ll$#!t Artist

Accelerated Development: When BA means B∪ll$#!t Artist | Accelerated Development | Scoop.it

BA typically means Business Analyst, but what makes for a good BA?  When do you have a good BA and when don't you?


A simple 3 question test that can determine if you have what it takes to be a business analyst

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Who should set defect priority?

Accelerated Development: Who should set defect priority? | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

Surprisingly, defect priority should not be set by QA. QA are generally the owners of the defect tracking system and control it, but this is one attribute that they should not control. The defect tracker is a shared resource between QA, engineering, engineering management, and product mangement and is a coordinating mechanism for all these parties.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Don't manage enhancements in the bug tracker

Accelerated Development: Don't manage enhancements in the bug tracker | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

When QA assigns enhancements directly to developers the issue ends up bouncing around to different people like a hot-potato. Why enhancements should not be recorded but not managed like other defects in the bug tracker.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Size Matters

Accelerated Development: Size Matters | Accelerated Development | Scoop.it

We say software development is difficult because of complexity; however this definition is useless because it does not help us reduce complexity. Here we define complexity, concrete ways to reduce it, and explain why "size matters"

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Who needs formal measurement?

Accelerated Development: Who needs formal measurement? | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

We all know the expression "You can't manage what you can't measure", but do we really understand it?

After execution, feedback is an essential part of all processes. Just think about how difficult it would be to drive from home to work wearing a blindfold.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Stop It! No… really stop it.

Accelerated Development: Stop It! No… really stop it. | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

There are 5 worst practices in software development that if stopped immediately will improve your productivity by a minimum of 12% and improve quality by a minimum of 15%.

These practices are so common that people assume that they are normal -- they are not, they are silent killers wherever they are present.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Inspections are not Optional

Accelerated Development: Inspections are not Optional | Accelerated Development | Scoop.it

Inspecting artifacts goes well beyond simple code inspections and can make a huge difference in software quality and reduce time to market. Few companies do inspections and fewer do them properly.

Why artifact (use case, UML, code, test case, etc) inspection is not optional if you want to build quality software systems.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Uncertainty trumps Risk in Software Development | Accelerated Development

Uncertainty trumps Risk in Software Development | Accelerated Development | Accelerated Development | Scoop.it

Successful software development involves understanding uncertainty, and uncertainty only comes from a few sources in a software project. The uncertainties of a software project increase with the size of the project and the inexperience of the team with the domain and technologies.The focus on this article is on uncertainty and not on risk.

 Learn why understanding uncertainty in software development is much more important than understanding risk.  

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Pair Programming for Team Building

Accelerated Development: Pair Programming for Team Building | Accelerated Development | Scoop.it

Pair Programming only has marginal advantages during development because it ties up 2 resources.

 

Instead, it can be used as a team building tool judiciously to improve team chemistry and promote sharing of individual productivity techniques..

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Infeasible Projects: Executive Ignorance or IT Impotence?

Accelerated Development: Infeasible Projects: Executive Ignorance or IT Impotence? | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

Infeasible software projects are launched all the time and teams are continually caught up in them, but what is the real source of the problem?

There are 2 year actual projects for which the executives set a 6 month deadline.

The project is guaranteed to fail but is this due to executive ignorance or IT impotence?

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Seriously. The Devil Made me do It!

Accelerated Development: Seriously. The Devil Made me do It! | Accelerated Development | Scoop.it

Quite often we make sub-optimal or ethically ambiguous decisions under pressure and avoid doing the correct thing.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Agile tools do NOT make you Agile

Accelerated Development: Agile tools do NOT make you Agile | Accelerated Development | Scoop.it

Great tools don't make you better unless you know how to use them.  So why would Agile enabled tools make you more agile unless you understand Agile first?  Why you need to understand agile principles for either JIRA or Version One to help you

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: The Programmer Productivity Paradox

Accelerated Development: The Programmer Productivity Paradox | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

We often hear that writing code is the most important thing and that there is not enough time to write it.  But is this true?

 

Developers are at their desk all day; they dislike meetings because it interferes with writing code. Yet, we can demonstrate that only 5% of their time is actually tied up in writing code -- so what are they doing with the rest of their time?

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: What the Heck are Non-Functional Requirements?

Accelerated Development: What the Heck are Non-Functional Requirements? | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

Simply put, if functional requirements create code that will address the needs of the end-users (customers), then non-functional requirements address the needs of the people who install, operate, and configure the code.

more...
Esta Lessing, CBAP®'s curator insight, December 29, 2013 11:47 PM

Some great examples and explanations of what non-functional requirements are! Enjoy!

Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: It's not a bug, it's...

Accelerated Development: It's not a bug, it's... | Accelerated Development | Scoop.it

Bugs, or defects only happen when developed code functions differently than the requirements.  What we should do in the presence of poor or missing requirements when we know the behavior is wrong.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Let the Machines Take Over

Accelerated Development: Let the Machines Take Over | Accelerated Development | Scoop.it

We write software because it is clear that automation can make a difference. We know that automation helps when building software, but it is hard to convince management to buy those tools. Here are statistics to help you win that battle with management -- in particular, automated static analysis can raise code quality by 31%!

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Stupid is as stupid does

Accelerated Development: Stupid is as stupid does | Accelerated Development | Scoop.it

7 out of 10 software projects fail, many of them before the projects even starts. A technique to get senior management to reconsider risk in a software project before it starts.  Prevent bad projects from getting started.

 

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Defects are for Losers

Accelerated Development: Defects are for Losers | Accelerated Development | Scoop.it
Dalip S. Mahal's insight:

A developer is responsible for using any and all techniques to produce defect free code. Before reaching for a debugger, note that there are 5 other points in the software creation process where you can detect and get rid of defects. Do you know and use all of them?

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: No Experience Required!

Accelerated Development: No Experience Required! | Accelerated Development | Scoop.it

Did you know that we have never found a relationship between a developer's years of experience and code quality or productivity? We have measured this at least 8 times over 30 years and the results have not changed!

Without regard to legality, this suggests that expensive poor performers should be replaced with inexpensive good performers.

more...
No comment yet.
Scooped by Dalip S. Mahal
Scoop.it!

Accelerated Development: Bug Tracker Hell and How To Get Out!

Accelerated Development: Bug Tracker Hell and How To Get Out! | Accelerated Development | Scoop.it

Bug trackers are like a roach motel, once defects get in they don’t check out! Because they are append only, shouldn’t we be careful and disciplined when we add "tickets" to the bug tracker? We should, but in the chaos of a release (especially start-ups :-) ) the bug tracker goes to hell.

Bug Tracker Hell happens when inconsistent usage of the tool leads to various problems such as duplicate bugs, inconsistent priorities and severities. While 80% of defects are straight forward to add to the Bug Tracker, it is the other 20% of the defects that cause real problems.

more...
No comment yet.