On this Indonesian video, we show you to understand what requirement engineering in a software product. And how to make sure you can build better software by applying requirement engineering. This video describes 5 things do and dont in requirement engineering.
//
If you have ever need to learn project management deeply by understanding every fundamental aspect. This article will cover you what need to be learnt for project management. Project management that I said is pragmatic project management. this learning guide is not ittended for PMI certification but might be usefull for your quick and daily activity when you managing the project. Before we start we need tools like Microsoft Project Office 365 Subscriptions Office 2013 or Office 365 Pro Plus Subscriptions Season 1 – Thoeritical Week 1. Understanding Project Management Fundamental You should know what is project, what is project management, who is the stakeholder, and how to measure the successful of a project. Week 2. Project Management Lifecycle You need to know what the steps to create the successful project whether using conventional or agile process. Week 3. Getting Started a Project This theory covers what you need to propare to start a fresh project. Week 4. Project Planning and Estimation On this week, we will learn about how to estimate and to plan a project by understanding estimation fundamental, estimation verification, and measuring estimation. Week 5. Budget Planning On this week, we will propose a project budget based on the project planning and estimation step. we will also learn how to understand the budget component, overhead, and budget negotiation. Week 6. Project Management Tools In this week, we will discuss the known project management tools. we will choose on of the famous project management tools like Primavera, Open Project, or Microsoft Project to implement the fundamental aspect of project management. Season 2 – Practical Week 7. Creating Project Proposal The practical session deep focused on daily task on your project management. this week will discuss the project proposal that contains the scope of work of our project, investment budget, timeline, and many others detail. Week 8. Managing a Meeting This practical tips will handle a meeting as a fundamental of client satisfication. This cover preparing a meeting, creating a meeting schedule, managing agenda, executing the meeting, and creating the side notes of meeting. Week 9. Creating a project team This week will discuss how you compose the project team, when will you need additional team member, and when you need the consultant or the bigger team. Week 10. Running The Project This week will discuss how to steer a project, keep the project rhytm works well, and understanding the basic control management to run the project. Week 11. Managing Technical Documentation This week will dicuss the technical documentation that might be needed as an artifact of the project. Week 12. Project Deliverables This week will discuss how to setup deliverables, deliver the project, create a training session, and launch the project. Week 13. Completing a Project This will discuss how to complete a project, how to create better ending, creating portfolio, and composing a prokect knowledge based for the next project. Week 14. After Project Support This week will discuss how to setup long term commitment to support and to operate a project result. as well as to make an opportunity to the next project. That’s it our learning plan to understand project management better, and hopefully with 14 week (@2 hours) you will get better understand your project. If you need a learning kit, or even onsite training about this project management you can contact me through email, see you
Contract is something common that happen on a project. Ideally contract will cover resources, budget, and time constraint. It covers the features, the time, and the budget is needed. Contract is fragile on a project. Sometime, client want a new feature, a team has limitation to solve problem, or even client can pay the cost on time. On ALM minimalist there are two type of contract which are Optional Scope. Optional scope means the scope will flexible with fixed developer resources and fixed developer time Cost Scope. Cost scope means the scope will fix on cost and time. This contract will good for a specific deliverable date and fix time but flexible resources. The contract should be prepared on initial planning before the iteration. It covers several points such as Project background. The background problem of project (Why) Mission Statement. It should clear show what to do on the project. It inspires to stakeholder and inspires a framework to make decission making. (What) Methaphor. It should show a simple analogy of the project features. (How with ‘Simplicity’ on mind) The time boxed. The time needed to implement the features. (When) On DSDM (Dynamic Software Development Model) the good way to validate contract with customer is through a term called Blitz Planning. Blitz Planning is rapid planning to propose the non technical aspect of the project like Resources, Budget, and Time Good Book to Read
You might ask several people what we need to prepare to close the project. The answer is sample "anything that we have as a project result". Anything can be your product (Software) and its related artifacts. If your are working with a limited team you can adopt my Global eXtreme Programming (GXP) Project Documentation. GXP provides several artifacts such as
Project overview statement. This section provides global way to tell how valuable your project. The business problem, the business need, and the benefit
Project deliverables. What you have after the project is finished.
Project management. The team, the role and the supporting organization.
Project solution. The engineering stuff such as the requirement engineering, the project design, and project result.
Project audit. Resource, budget, and time audit
You can download the template here
This bahasa tutorial will cover basic understanding of project management budgeting techniques. Enjoy 17 minutes of this screencast video
Someday we face a problem that our project is not totally collocated, some of the team member might be separated geographically some of them might be have different discipline or come from others company. Right tool can be worked as practical solution to solve communication,coordination, and control challenge (I said it as 3C challenge). So if you feel tedious with the framework like GXP or others distributed framework. You can think simple by adopting agile and choose the right tool.
Adopting Agile Project Management
Agile project management is a way to manage project in essential manner. For example rather to create a lot of meeting, agile project management focuses in creating a short meeting using technique called as “sync meeting” or “stand up meeting”. Another example, when we face a long coordination meeting in the end of the project, we manage the coordination meeting incrementally in several iteration
Step One – Choosing Your Agile Method
Starting from eXtreme Programming, Scrum, ICONIX or your homemade Agile method. Choosing one and discuss the method with your peers. Some of method might be need further modification when you implement it in distributed project. For example, including the customer in distributed project when your customer is oversea will be cost too much. There is no rule of the modification but as long as you can make the team and client get in touch closely you done it
Step Two – Client is fragile so don’t break them
Communication is the main issue of distributed project. Please take care your client by contacting them in a rhytm. I mean contact them regularly in a week or two. Send them newsletter about their project. Update them with technology and case study. Transparent for the issues in their project as soon as possible. Client is fragile if they are too busy for you, it might be great if you cancel the project before you start. But when you already agreed with the project take care them just like a glass. Money is not everything
Step Three – Hear The RBT Sound
RBT (Resources Budget and Time) is the most sensitive information in the project world. Taking care the RBT means you handle the project. For example if your developer leave you have the spare, when the requirements change you can facilitate and negotiate with them. And in the end you can handle the project if you can get revenue from the project
Step Four – Choosing The Project Management Tools
You can find a good tool like Project Server, Telerik Team Pulse or even Team Foundation Server. Stop Now, I will discuss the further in the next blog post stay tune.
@ridife