Read: 1170 times    -     Avarage Rate: 4.7

2010 16 Oct

After three months of hard work, Agile Manifesto is now available in Arabic. Mohamed Elamery, Sif E. Elharti, Karam A. Labban and I (Hasan Jaffal), worked on translating these rules that rule the world of agile project management worldwide. In order to succeed in the new economy, to move aggressively into the era of e-business, e-commerce, and the web, companies have to rid themselves
Read: 1064 times    -     Avarage Rate: 3

2010 08 Jul

PERT introduces risk onto the project schedule via 3-point estimates of activity duration when deterministic time is unaffordable. This practice propagates the notion of risk over the scope of the project and allows for a feedback into the financial decisions pertaining. We shall start by introducing the risk profile of the activity and its rationale then proceed to its effect on the whole schedule and deadline. Afte
Read: 1871 times    -     Avarage Rate: 3.5

2010 08 Jul

I searched the internet about the best ways to represent the use cases and the user stories in agile project, I faced many points of views that fit all in the same basic standard format: As an <actor> I want to <action> so that <achievement> This way of representing a user story is indicative and helps explaining the needed requirements to team members, but in big systems where the number of user stories is h
Read: 1220 times    -     Avarage Rate: 4

2010 28 Jun

Currently, I am initiating a new project and building its team and giving the responsibilities and missions for the people working with me. Without any researches or waste of time,  and as always in such situations I came back to the God of leadership John Maxwell, who says “to build a successful team, you have to add people who make things happen, you need a catalyst in your team”.
Read: 2424 times    -     Avarage Rate: 5

2010 07 Jun

In traditional projects, and the old life cycle management methodologies, the requirements changes were so hard, and the teams try to resist it as possible. So the detailed requirement catching was the first goals of project. So to minimize the changes in the requirement team shall include whatever they can imagine in their analysis and have to see the and predict the coming path for the software in order to minimize the final cost.
Read: 2117 times    -     Avarage Rate: 4

2010 18 May

The decisions within an agile development project must be the responsibility of all team members, especially the Active users, from here come the importance of the active user involvement. The project team must be empowered to make decisions in order to ensure that it is their responsibility to deliver the product and that they have complete ownership. Any interference with the project team is disruptive and reduces their motivation to deliver.
Read: 2484 times    -     Avarage Rate: 0

2010 17 May

In all development projects, the sales describe the requirements to the client who will understand them in his own way while the development team will understand these requirements in a third way.
Read: 3912 times    -     Avarage Rate: 3.5

2010 17 May

Understanding Success The traditional definition of success is the delivery on time, on budget, and according to specification. [Standish] Agile Methodology When developing software, there are two basic approaches to planning: waterfall and agile. In the waterfall model, the project is planned, Scheduled, Built, Tested, and then Deployed, the larger the project, the more problematic the waterfall metho
Read: 4879 times    -     Avarage Rate: 4.2

2010 31 Mar

Introduction In Agile projects, it's a common practice to visualize and share project status using charts or diagrams on boards. While no single document delivers all of the ammunition agile teams need to get the rhythm, this set of visual materials offers an easy framework to help guide software development teams through the various agile cycles. "Kanban," in Japanese means, loosely translated, 'card or sign'. Kanban is a method which uses standard units